Is there an "official" precompiled release for win32 and/or win64? If that were the case I would just use that, and bring it into my cross environment. On the other hand, if the standard installation is for one is to build their own for maximum tool chain & platform compatibility, then cross compilation is more of valid concept. In my case plplot itself is one of many dependences. As with builds for embedded targets for instance, when creating home built dependencies is required or desired, configuring them for the minimal feature set needed is common. So from that perspective, a custom stripped down build of plplot without dynamic drivers that would likely only be deployed as a dependency of another project is not really a problem. Especially if that allows for larger goals to be achieved - in my case a linux hosted, multi targeted continuous integration environment.
The cmake build system of course is still used for a native linux build. However I also target things like embedded arm linux environments with cross compilers, and so I might handle them the same way (I have to deal with things like problems from mixing object code from different gcc versions). With luck I'll get cmake cross builds working as well. In the mean time if someone wants, I can make a wiki page or something explaining how to do it this way. Hopefully I can at least get a "feature complete" version in action, even if it lacks all the drivers and bindings. Again I'm so thankful for plplot existing, and I look forward to contributing in some way. Werner Smekal wrote: > Hi Alan and Thomas, >> >> Once you get that first simple cross-build working properly, then I >> think >> the next step is to figure out what to do with dynamic devices. That >> does >> work on MinGW so it should be straightforward to get it to work for a >> Linux >> cross-build for MinGW, but I am not familiar with the MinGW dynamic >> device >> details so someone else will have to help you there. > This should work "out of the box" since on Windows there is no library > provided at all by MinGW or Visual C++. I wrote replacement functions > for the used libltdl (?) functions which are compiled and linked in if > cmake has WIN32 set. So this should be no problem, but if dynamic > drivers are enabled, get-drv-info.exe is run for every device during > the compilation to create some files - this would already need Wine I > think. I'm not sure if this "just works". > > Regards, > Werner > ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Plplot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
