Bred Schmidt wrote:
>> http://seriss.com/people/erco/fltk-videos/
>
> thx for the video link. solved my problems.
> i didn't know that precompiled headers should be inactive. and the rest was
> just because i didn't linked to the libs (although i did already).
The precompiled headers are optional.
When I build makefiles for windows, I turn em off.
> do i have to add /Ic:\fltk-1.1.9 and under linker c:\fltk-1.1.9\lib\fltk.lib
> wsock32.lib comctl32.lib always, because i think i have added them already
> somewhere.
Depends on where you have that info added.
The /Ic:\fltk-1.1.9 is only needed for the compile stage,
and the c:\fltk-1.1.9\lib\fltk.lib is only needed for the link stage.
You should be able to see these flags in the build log.
Be sure the compile/link lines look similar to the FLTK default build.
Hopefully the way the video shows how to add these is still relevant;
sometimes microsoft changes the GUI interface around.
> can i set this somewhere, so that i don't have to type it everytime i want
> to program?
I don't know, I assume there's ways to make templates in Visual Studio,
but I've never done that.
Even though I made that video, oddly I'm probably the /last/ person
to ask, as I never use the IDE for building under windows.. I always
use the command line + makefiles. I had to kind of 'learn' how to do
the GUI just enough to make the video, cause so many folks were asking,
that I felt motivated to make it.
Some of the other folks here use the IDE, they might be able to tell
you.
If it were me, once the hello world works, I'd just copy that project
over to start new projects.
> btw: the hello-world programm doesn't work for me in your video
If you can supply details about what didn't work, I can try
add comments in the webpage about what changes are needed
for the newer compilers.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
