Problem with FLTK wizard

[ncassetta]

I am trying to use CodeBlocks with FLTK library. The wizard ask me to specify the folder where FLTK is unpacked, saying "this folder must contain the subfolders "include" and "lib"". But FLTK doesn't have an "include" directory, it has "Fl" instead for header files. So the wizard says me he can't locate the include directory and stops.
I tried also to edit the #fl global variable, with Settings=>Global variables, setting ...\fltk-1.3.3 as base directory and ...\fltk-1.3.3\Fl as include, but this also fails, saying "The path you entered seems valid, but this wizard can't locate the file Fl.H in it." Obviously I checked it and the file is there.
Thanks for your attention
N. Cassetta

[oBFusCATed]

I guess the wizard is made for different version of the library. You have to either create the project from scratch or modify the wizard to work with the current version and provide a patch. The wizards are simple squirrel scripts, so it should be an easy task to adjust it. To see the script right click -> edit script in the wizard dialog.

[ncassetta]

I have no experience with squirrel, but I think I've understood what happens.
The structure of FLTK dir is this (for every Windows version):

fltk-1.3.3                    -> base dir
    FL                           -> include dir
        Fl.H                     -> header files
        . . .

The wizard, instead, thinks this:

fltk-1.3.3
    include
        FL
            Fl.H                   -> header files
        . . .

so it verifies if the base.include/FL dir contains the Fl.H file and fails. A comment in the script says that this only applies to Windows.
I have found a workaround setting for the global variable fl:
base dir -> fltk-1.3.3
include dir -> fltk-1.3.3 (the same, so it searches in fltk-1.3.3/FL)
and it works, but I think this is rather confusing.
I am not able to correct the code, but probably the person who made the script could revise it in few minutes

[stahta01]

The problem likely is for some windows Compilers the script works correctly.

Tim S.

[oBFusCATed]

Most of the wizards are user contributions, so I doubt anyone will do it.
Why do you think you cannot modify the code?
If you're able to read it then you should be able to modify it.

[oBFusCATed]

The problem likely is for some windows Compilers the script works correctly.

What do you mean by this? The wizards most of the time doesn't care for the used compiler.

[stahta01]

The problem likely is for some windows Compilers the script works correctly.

What do you mean by this? The wizards most of the time doesn't care for the used compiler.

Have you not noticed that the path for including headers are different for MS Compilers and GCC Compilers.
I have tried many times to fix the SDL Wizard and finally gave up.

Tim S.

[oBFusCATed]

No, I've not looked at the wizard.