On 1/11/08, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote: > Jorge Schrauwen wrote: > > > > libaprutil is still set to x64 instead of win32 when compiling under > > 2008 but I take this will get fixed in the win32 src package > > No; you set it; that is to say that visual studio is bugged, and VC6 > .dsw did not specify per-project dependencies, VS .sln migration makes > foolish associations. This is even true when I introduce x64 targets > to all projects, it has nothing to do with the source .dsw/.dsp files. > You need to update these; there may be a separate package that offers > .sln's at some point to fix VS bugs, haven't decided. (The src package > is intended to be built from exported .mak files). > > > multicast.c is still broken using vs 2008 with the latest platform > > SDK, vs 2005 with the older platform SDK works fine! (there is a patch > > for this... IIRC its also in apr trunk but it was laten when I was > > talking about this with wrowe I can't remember for certain) > > It's also on apr branches but not yet released; > https://issues.apache.org/bugzilla/show_bug.cgi?id=40398 > > the patch applied to apr was the Cleaner and not Dirtier flavor. > > It will hit the next 1.2.x apr release, I'd presume there will be one > sooner or later. > > > FWIW: BuildBin's installdir is still set to /apache2 instead of > > /apache22 not that will effect anything just something I noticed. > > Yup - no impact, not likely to change. > > > The /machine not set warnings are still there aswel but again no > > problem here since it defaults to x86 > > or defaults to x64 using that compiler/linker. Again, goofy win32 > behaviors, and can't be fixed without x64 + win32 (x86) targets which > would permit compilation using two-different targets. > > It was more than I wanted to mess with for this point bump, but will > probably get back to that issue over the next several weeks. > >
I'd be willing to generate and package vs 2008 sln and fix the apr-util goofyness. Say if solution files are created... do we want different packages for 2005, 2008,...? 2008 is said to be compatible with 2005 but opening a 2005 sln in 2008 it still randomly changes settings and such. Say if I create such a extended package based on the office 2.2.8 win32 src do you think that could be useful? I can always place it on my own website for interested people but I suspect it won't get much attention there and won't be worth the hassle. -- ~Jorge
