I’m not sure if I should just start posting my compiled versions (potentially wrapped in a nice installer) here.

Yes, while the official bindings are built, I am yet to see 1.6.9’s — it’s been nearly a month! I needed the binaries for a few servers so I decided to spend time and build it myself…

I could probably whip up a build script to automate most of the process, but it looks like the “official” SVN-python bindings are being kept up-to-date now.

In the trac ticket you mentioned, someone did nail it down to a change in the declaration of _apr_time_ansi_put (@12 vs @8, which took me 4 hours to nail down, urgh!) The declaration of apr_time_ansi_put takes a time_t argument, which until VS2005 was typedef’ed to an int; after which was typedef’ed to an long long. Thus, the size of time_t changed between versions of VS. Since we’re compiling on VS2008, time_t defaults to 8 bytes (64 bits)

Since the compiler tacks on the size of the arguments to the function to the end of the function (the @x bit) our VS2008 declaration has a different name from the one declared in libapr-1.dll (which, presumably is compiled on an earlier version of VS). This results in our entry point not found error when using the binaries from within Apache (because, since the httpd’s libapr-1.dll is already loaded in memory space, when the svn-python dlls import libapr-1.dll, they get the httpd copy and not our own)

Hence, I would imagine a better solution would be to define _USE_32BIT_TIME_T (see: http://msdn.microsoft.com/en-us/library/4wacf567.aspx) when building the projects which reference time_t (which is most of the SVN libraries) It’s really tedious, so one may decide to modify the VS header files to define that preprocessor variable and remove it when we’re done compiling svn-python.

Application.ActivePrinter = NetworkPrinter(“PS_Printer”)

The NetworkPrinter function tries to detect which port the printer is on and set the printer string accordingly. If the string doesn’t resolve to a proper printer (“PS_Printer on PS_Port”) it will use the default printer.

Alternatively you can of course set .ActivePrinter = “PS_Printer on PS_Port” directly – the NetworkPrinter is more for when you use a physical printer which may or may not be on the same port on each computer in a network.

Thanks for the article, I think it may have solved a very big problem for us. However, I have a problem getting it to work, unfortunately. I have set up a dummy printer (call it “PS_Printer”) on a dummy port (“PS_Port”), and used the following code:

ThisWorkbook.Sheets(SheetName).ActivePrinter = “PS_Printer”
ThisWorkbook.Sheets(SheetName).PrintOut(FileName:=strFilename, Copies:=1, PrintToFile:=True, OutputFileName:=sOutputFilename)

..but the application still tries to print to the default printer. Have I missed something? I have tried using the dummy printer from Word, and it seems to work just fine, so I’m wondering if the code is somehow “missing” the dummy printer.

Any help would be very gratefully accepted!

Notable changes:
- apr_* will build, but have 8-9 failed builds – the database modules won’t build unless you add in the proper libraries, which is outside the scope of this article, for now.
- You might have to force VS2008 to recognize where your python.exe is found (Adding the path manually in options), otherwise some parts of the base library will build successfully (or so it seems), except there’s a line about not finding “python”, and nothing is really built.

After a bit of work I got it to build, but the finished product, the .pyd/.py files, don’t work…