On 01.05.2010, at 23:16, Greg Ercolano wrote: > Matthias Melcher wrote: >> Those files are generated by Fluid. Better to change the Fluid code than to >> modify the VisualC6 files! It's in ide_visualc.cxx . I'll be happy to fix it >> when I find the time. > > Good to know. > > What I'd like to do is fix the *.dsp files that are currently in SVN, > so people checking out fltk 1.3.x now can build correctly.
Yes, running fluid with the right parameters will generate those files. You can then commit them. > I imagine the .dsp files don't get changed unless manually runs > some operation (distribution prep maybe?) that changes them all, > and then the dev would have to commit the changed files to SVN > to affect user builds. > Curious: what operation would cause fluid to recreate all the .dsp > files? > Is that a distribution prep step? * fluid -dsnvsjvk usage: ../fltk-1.3.0/ide/Xcode3/build/Debug/Fluid.app/Contents/MacOS/Fluid <switches> name.fl -c : write .cxx and .h and exit -cs : write .cxx and .h and strings and exit -o <name> : .cxx output filename, or extension if <name> starts with '.' -h <name> : .h output filename, or extension if <name> starts with '.' --dbmake <dbname> <targetpath> : create all IDE files for a Makefile/autoconf based project WARNING: --dbmake is not yet implemented completely. --fltkdb <filename> : create a database describing all FLTK project rules --dbvisualc6 <dbname> <targetpath> : create all IDE files for an Xcode3 project --dbxcode3 <dbname> <targetpath> : create all IDE files for an Xcode3 project (...) --fltkdb is not needed because the database is in the svn repo. just change to the FLTK base directory and run: * fluid --dbvisualc6 fltk.db . and it will generate all required VisualC6 files. This should work on all latforms. If it does not, you may have to add the ide_*.cxx files to the Fluid build setup. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
