Albrecht Schlosser wrote:
> DEP_CPP_FL_TR=\
> DEP_CPP_FL_TR=\
> DEP_CPP_FL_TR=\
Oh yeah, I did catch that and fixed it, but I forgot to
update the tar file.. thanks for catching that!
> WRT svn properties: most of the files obviously have "binary"
> attributes ("svn:mime-type application/octet-stream"), but some
> have "svn:eol-style CRLF". I'm not sure which one is better, but
> I think that we could set "svn:eol-style CRLF", since all files
> are text files, as you wrote before.
OK, I'll check the /new/ files in with the "svn:eol-style CRLF"
so that if nothing else, they can be svn diff'ed.
> Okay, I just tested it with a local svn repository: as I assumed,
> we can see differences if the file has text format ("svn:eol-style
> CRLF"), but there's no diff, if the file is binary (and, IIRC,
> internally (in the repository) the binary file is saved completely
> and not as a diff. It seems to work though, and since some of the
> files *are* already checked in as text, I think that we could try
> to make them all text with CRLF. Maybe...
Right, I was noticing that as well (inability to diff).
I figure they may have made those files binary 'just to be safe',
in case the text included inline binary or pseudo-binary data
(icons, non-utf8 unicode, or who knows what Microsoft might do
in those files)
From what I can tell, they're pure ascii, and I hope they
stay that way, and human readable. Unlike the SLN files that
have GUIDs all throughout.
Will follow up on the rest of your msg after I update my
tar file, but following up on this:
> Questions: Greg, can you open the project files in ide/vc2005,
> and if yes, what is the default configuration, and what
> happens if you compile and build with them? I assume that
> your previous tests all were with ide/visualc, right?
The default config is 'Debug', and only 'Release' and 'Debug'
are the options there.
And yes, I was only using ide/visualc/fltk.dsw, I did /not/ mess
around at all with the ide/vc2005/fltk.sln file, which I guess is the
"more modern" VS data format that even my VS7 seemed to prefer saving
in.
And yes, it's full of GUID hex code madness (similar to the Apple Xcode
files).
There didn't seem to be a way to "Save As" a .dsw file from my VS7,
only .sln. Which is one reason I went to text editing the files.
The other reason was the sheer insanity of checking all those damn
file properties from the VS Gui.. there were like 50 or so screenfulls
of data that had to be checked, and many fields were different because
my VS7 has different defaults from the original VS that made the
fltk.dsw file.. IDEs are madness in that respect!
> These files look much more complicated though, because they
> are in XML format and make intensive use of GUID's.
Right, a reason I won't touch the stuff.
I figure folks who understand the new VS IDE better than I know the
quick way to add the new files to those modern project files, other
than having to visually compare all the properties through those teeny
dialogs (that aren't even resizable..!)
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
