From: Bruce S. <Bru...@nc...> - 2006-11-30 23:34:38
|
I'm not using any special build tools. But as of a few minutes ago=20 there's a beta8 with many improvements. On Windows Arthur and I are currently using MinGW in the Msys=20 environment (though Arthur is interested in trying the Microsoft C++=20 compiler instead). On both Windows and Ubuntu I'm following the=20 instructions in INSTALL.txt, which have been significantly simplified=20 for Windows thanks to Arthur. You are correct that there is some leftover irrelevant stuff having to=20 do with the fact that at one point Jonathan Brandmeyer investigated=20 using scons instead of more traditional build tools. Bruce Sherwood Dethe Elza wrote: >On 30-Nov-06, at 5:52 AM, Arthur wrote: > > =20 > >>I am concerned that you are working not at the bleeding edge, but =20 >>beyond >>it a bit. And are trying to solve problems that shouldn't be yours =20 >>- in >>that beta8 is a work in progress that has been focusing not only on >>numpy compatibility but on some Windows specific build issues, and =20 >>that >>there has been some futzing with Makefile.in (that I think Bruce =20 >>checked >>in) that address those, but without, at the moment, thinking =20 >>through the >>crossplatform implications, mainly because we haven't finalized =20 >>what the >>keepers are, even for Windows. >> =20 >> > >I was trying to build from the beta5 tarball, but the files Martin =20 >was using weren't in it (there are several build tools involved--not =20 >sure how/where pycompile, scons, or mkdist_osx.sh enter into the =20 >process (are they used, or just cruft left from earlier builds?). On =20 >the other hand, now that I have gotten it to build and run (see my =20 >reply to Martin following this), I can try to repeat the process from =20 >the beta5 tarball, or selectively roll back what I have checked out =20 >from CVS. > > =20 > >>That being said, I think Bruce successfully did a Linux build from the >>cvs as late as yesterday with no apparent problems. >> =20 >> > >Excellent. Bruce, if you're reading this, could you give me some =20 >insight into which of the build tools you're using? > > =20 > >>Coming in late, but looking at your build log where everything looks >>rather sensible. >> >>Is it clear where -lboost_python -lboost_thread are being found. >> =20 >> > >Martin had given me the key to this in an earlier message, but I had =20 >missed it. Got it now. > > =20 > >>Presumably you are using a binary distro of these libs that are =20 >>placing >>them somewhere standard. I mention it because when I have built those >>libraries, on Linux, or Windows I have had to handle them with kid >>gloves, re: naming and install issues. >> =20 >> > >I'm using Fink to build all of the libs. > > =20 > >>Beyond those clues, which might not be clues, don't have a clue =20 >>what you >>might be running into. >> =20 >> > >It's all helpful. Thanks, Art! > > =20 > >>Art >> =20 >> > >--Dethe > >values of =CE=B2 will give rise to dom --Unix prehistory > > > >------------------------------------------------------------------------= - >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share = your >opinions on IT & business topics through brief surveys - and earn cash >http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV >_______________________________________________ >Visualpython-users mailing list >Vis...@li... >https://lists.sourceforge.net/lists/listinfo/visualpython-users > =20 > |