> Op maandag 7 augustus 2017 11:21:37 UTC+2 schreef MacArthur, Ian (Leonardo, UK):
> > Hi there, I am working through Bjarne Stroustrup Programming Principles
> > and Practice right now and I struggled to get fltk-1.3.4 and Visual
> > Studio 2017 Community going. Finally I figured it out and made a little
> > tutorial for anyone who also needs help. (I know you could/should
> > potentially do it thorugh nuget, but this is the manual "hard way" I
> > suppose.) Let me know what you think. Cheers, Phil
> No, it's not the wrong place, and in general it's a very nice howto
> you have created - might be nice if you could add a link to it from
> our howto's as well, in the hope that might others to find it.
> Once caveat however: I note that you recommend that folks copy
> the fltk build-products and headers into the VC tree, so that VC
> can easily find them...
As Ian wrote, we do need to clean up the FLTK README files.
They need to be (1) consolidated and (2) simplified.
And that old recommendation to copy the FL directory
into the VS include directory seemed like it was introduced
waaay back when FLTK was ported to Windows, and either the compiler
had some weird limitation or our porting developer couldn't figure
out a better solution.
Unfortunately that hack recommendation was not removed, and
was left in there for way longer than it should have.
> Now, I accept that this suggestion is widely repeated "wisdom"
> and appears in many places; many other projects do it, IIRC fltk's
> own WIN32 Readme suggests it, Dr.S's notes (at least used to) suggest it, etc...
> But it's actually a Really Bad idea, since it can lead to all manner
> of pollution of the VS project space. It is far better to add the include
> and library paths to your project, to point at the fltk build-products
> in their native build directories.
Right -- we can't really blame Dr. S for any of those recommendations.
It must be hard to write a book, because once it goes to print,
you can't make bug fixes or track future changes.
We have had the very same Windows build technique of supplying
pre-packaged IDE files with our distributions.
It's only recently in the yet-to-be-released 1.4.0+ that we switched
to CMake to create the IDE files. And that seems to be working pretty
well for both old and new compilers. I just now used CMake to build
FLTK 1.4.x with the very old VS7 compiler (circa 2006) and it worked
just fine using the instructions in section 2.4 of the README.CMake.txt
On 12/12/17 11:47, Bjorn Hendriks wrote:
> Soooooo much Thanks and !@#&^ you Bjarne stroustrup !!! get updated
> you sell books for €60 but can do it thanks works for if i click
> on the .sln after trite his method. Works Thanks spend €60 on
> this book need to learn c++ a get a master have the second book on the way
Well, let's not be too acerbic; gotta admit I've been using C++
a lot in my career since 1993.. it bought me a house and kept food
on the table..
I can't really blame him for the trouble you had building FLTK,
that's more on our end of things I'm afraid ;) Though some blame
goes to Microsoft for changing their frigging compiler so much
every few years such that old project files wouldn't build on the
newer compilers, and had to have multiple IDE dirs for each big change.
We do need better README files though, and I'm hoping that's
where we'll be when 1.4.0 releases; less of them and shorter/clearer.