On Fri, 2010-02-26 at 16:39 -0600, stan.mar...@l-3com.com wrote: > Update on my own post, regarding the "missing" files...
Hi Stan, et al, >> includes a number of files which appear to have moved ... In addition to the dependencies problems, mentioned by Reagan, this missing or moved files also adds to the windows build problems, since it is difficult to _ALWAYS_ keep the vcproj (or dsp in my case) source file set UP-TO-DATE. Some tricks I have learned over the years ;=)) (a) subscribe to the cvs logs, and then you will 'see' when files are added, deleted, moved, and you can incrementally adjust your local system of choice. (b) and/or learn to read the Makefile.am trail. In any download these can give good information on what is include in what is being built in *nix, what ever version you are building. As previously stated, Fred and others are doing their best to keep the 'projects' msvc files current, but that will not address what is in previous releases. My TSS system is unfortunately 'frozen' until I do a later update, last was Feb 14, 2010, so will always have this problem. But as you have found, it is usually not too difficult to do these source list modifications. You have not yet addressed 'missing' files, which only become apparent after the final link, with sometimes many 'unresolved externals...'. Here you must find the source file containing the missing function in either SG or FG, and add it appropriately to SG or FG solution, a sometimes tedious process. You need a windows port of 'grep', and I have my own find all - http://geoffair.net/ms/fa4.htm Again I usually check what I am doing with the Makefile.am set, but this too can be quite difficult, since both SG and FG are made up of many different libraries in *nix, before the final Main fgfs exe, thus are in MANY different folders... <christ...@freedomworks.ca> wrote: >> Few months back we spent a couple days trying to >> compile FG on Windows using the FG Wiki and did >> not have any luck. [snip] >> Geoff, I appreciate your efforts in creating your >> own custom build process but we could not get your >> files to work. [snip] >> Can someone explain why this has not been addressed? Wow, Christian, and the others in the 'we', you manage to put _ALL_ efforts down, even though you say you 'appreciate' something, without ever saying exactly _WHAT_ problems you had! Saying you did not have 'luck', or that it did not 'work', is a put down, without telling what was the reason for your problems. You asked back on Jan 4 - > Is there anyone that can give us some direction > as to building for Windows? and we responded, but you still seem unhappy? Your specific problems, what ever they be, can ONLY be addressed if we know exactly _WHAT_ problems are being encountered. I just read the wiki :- http://wiki.flightgear.org/index.php/Building_FlightGear_-_Windows and it looks pretty clear. Long and tedious, but clear! I put thousands of words into my build site, and hope I make it CLEAR ;=)) Again, as Reagan suggested, there is NO simple apt-get, yum, etc 3rd party dependency library install system available for windows, so you, the user, must do it yourself, and I know that can be difficult and FRUSTRATING. And this is made even more difficult due to the fact that OpenSceneGraph (OSG) not only uses cmake before msvc, and has its own dependencies, like jpeg, and png, but, since it is a BIG set of DLLs (shared libraries), there can be other problems at runtime. Installing DLLs, in windows, such that they are available at runtime, can be difficult to understand... And this is similarly true to a lesser extent with OpenAL, and alut, although in my case, their SDK makes things easier, and only leaves alut... And then there is the enormous set of boost headers... but thankfully no build required... In my TSS build system, I address this by forcing _ALL_ the prerequisite dependency sources to be downloaded first, and put in a STRICT source directory structure. Once this is done, my setupfg.bat will take over, create a copy work, and the build can be relative simple ;=() The projects/VC?? msvc files included with the source download addresses this by providing a set of pre-built binary libraries, and includes, thus less build from source needs to be done... something I will migrate my TSS towards... It seems more like a chicken and egg problem ;=)) Until there are MANY more windows builders, willing to contribute some of their time to helping others, honing down the possible build systems, adding fixes, even to the wiki, we will not have many more windows builders... So is the windows FG build being addressed? I think so, but we could always have more input from others, with constructive criticisms, suggested fixes, changes, ideas on the build and install system, etc, etc... and in my case this can be off-board, since it only involves me... And Stan, gently, I would get off the 'boost' questions ;=)) If you read back in the archives you will see there were many, MANY words said about this back then... accept it is here to stay, at least until you can contribute a single patch to fully address its removal without loss of any functionality... Or use the 'deboost' git branch offered by Csaba ;=)) My 10 cents ;=)) I know, far too long as usual... Regards, Geoff. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
