Re: [INTERNALS-WIN] Lib queries - cclient
[email protected] ("Steph Fox")
| Newsgroups | php.internals.win |
|---|---|
| Message-ID | <01af01c96179$93c13660$3ffc1f3e@foxbox> |
> Given that you should not mix different runtimes or architecture > builds, there is no double usages. The header may differ as well, > depending on the architecture/platform you are running on. PHP > branches will have different libraries versions, for example we use > ICU 4.0 in head, 5.3 uses 3.8.x. I only have VC 6, so I only have ICU 3.6. That's one of the easy ones :) > All in all, it is easier to simply duplicate the tree even for the > libraries where the headers are the same (like bz2). The *.lib have to > be duplicated most of the times as well (per CRT). Yes - but not when you only have one CRT. > the setvars only add bin to the path and set a couple of other things. > The VC environments are still done like before, They were done before using vcvars32. See, if you look at the files, you find out all sorts of whacky things ;) one of them is that vcvars bat loads the MS build environment and you can add to it, manually or otherwise, to tweak the setup. Since we don't use the GUI any more, I maintain a small collection of vcvars.bat files for different kinds of builds. (This would be equivalent to saving the info via the GUI.) I have specific shortcuts for each batchfile, so f.e. PHP 5.2 Debug doesn't get the same files as PHP 6.0 Release. or using the conf.bat > configuration file (see cvs/php-internals-win). The snapshots script > use it for example. I think I ran snapshots maybe 5 times in my life. As someone who is generally looking at a single area of PHP at a time, I generally only build the bits I'm currently interested in (and the bits that impact on them). The only person interested in how snapshots work is the person responsible for putting them online, the rest of us just want a simple setup that works out of the box so we can debug our own areas of code. Unfortunately anyone working on the src right now needs to build all three versions of PHP before committing anything, but we sure as heck don't want to build everything out of PECL three times (or even one time) too. >> What on earth is 'phpsdk'? Oh it'll be in that tools thing I didn't look >> at >> yet I guess... no thanks, I like to know what's happening on my box :) > > A prefix used for all the public scripts. Real tools will be added too > soon. Oh god. Sorry. - Steph > > > Cheers, > -- > Pierre > > http://blog.thepimp.net | http://www.libgd.org