#1 build system

closed
nobody
None
5
2008-01-25
2007-09-30
No

A)
Can you make cmake use standard configuration mechanism?
use fltk-config for complete paths and dependencies

B)
use of
#include <OpenEXR/half.h>
...
and
#include <lqt/colormodels.h>
...
Currently the path to the OpenEXR and lqt includes must
be explicitly specified, which is not needed.

C)
Environment variables are not used such as:
CFLAGS CXXFLAGS LDFLAGS

D)
You specify GLEW as dependency, but do not check for.
It took me a while to see how cmake accepts a variable
to point it properly to my local library path.

Otherwise the compilation run well.

Discussion

  • Kai-Uwe Behrmann

    Logged In: YES
    user_id=634841
    Originator: YES

    Have to add it is about 0.7.3 . Looks like 0.7.3 is
    not yet in a good shape anyway compared to to 0.7.2.

     
  • darbyjohnston

    darbyjohnston - 2007-10-01

    Logged In: YES
    user_id=1114113
    Originator: NO

    I'll change the includes and start using fltk-config, those should be fairly easy.

    I'm not entirely familiar yet with how dependencies are handled in cmake, I'll have to look more into it.

    Out of curiosity, what sort of system were you building on?

    Thanks, Darby

     
  • darbyjohnston

    darbyjohnston - 2007-10-01

    Logged In: YES
    user_id=1114113
    Originator: NO

    > Looks like 0.7.3 is not yet in a good shape anyway compared to to 0.7.2.

    Currently 0.7.3 is the development version which will undergo a number of changes while in "pre-release". Were there specific problems you were having with it?

    Thanks, Darby

     
  • Kai-Uwe Behrmann

    Logged In: YES
    user_id=634841
    Originator: YES

    x86 SuSE10.2
    djv_view could not see any file or directory. The file manager list was
    with out names. Possibly a callback thing?

    Thanks to point A.

    to B
    You currently use
    #include <half.h>
    and must specify /usr/local/include/OpenEXR where
    #include <OpenEXR/half.h>
    would be included by /usr/local/include
    The same for lqt. It is just a recommendation.

     
  • darbyjohnston

    darbyjohnston - 2007-10-02

    Logged In: YES
    user_id=1114113
    Originator: NO

    > x86 SuSE10.2
    > djv_view could not see any file or directory. The file manager list was
    > with out names. Possibly a callback thing?

    Which version of FLTK are you using? I'm currently building against 1.1.x-r5917.

    > #include <half.h>
    > and must specify /usr/local/include/OpenEXR where
    > #include <OpenEXR/half.h>
    > would be included by /usr/local/include
    > The same for lqt. It is just a recommendation.

    Will do.

    Thanks, Darby

     
  • Kai-Uwe Behrmann

    Logged In: YES
    user_id=634841
    Originator: YES

    I used 1.1.7. Ok with 1.1.x-5917 it is gone.

     
  • darbyjohnston

    darbyjohnston - 2007-10-10

    Logged In: YES
    user_id=1114113
    Originator: NO

    Hi,

    I just uploaded a new pre-release version (0.7.3-pre4) which has some of these changes to the build system. This mostly applies to the UNIX versions, the Windows version still has some parts hard-coded. Specifically:

    > A)
    > Can you make cmake use standard configuration mechanism?
    > use fltk-config for complete paths and dependencies

    Done.

    > B)
    > use of
    > #include <OpenEXR/half.h>

    This I didn't change; the pkg-config file that is generated with OpenEXR 1.4 specifies the full path to the header files.

    I also noticed that the pkg-config file, at least with the 1.4 version, seems to be missing the threading libraries; I had to change the library line to this:

    Libs: -L${libdir} -lIlmImf -lIlmThread -lImath -lHalf -lIex -lpthread -lz

    > and
    > #include <lqt/colormodels.h>

    Done. Plus pkg-config is now used to get the libquicktime information.

    > C)
    > Environment variables are not used such as:
    > CFLAGS CXXFLAGS LDFLAGS

    CXXFLAGS and LDFLAGS can now be used to specify additional paths and libraries. Only include paths, library paths and libraries are supported. CFLAGS is not used.

    > D)
    > You specify GLEW as dependency, but do not check for.
    > It took me a while to see how cmake accepts a variable
    > to point it properly to my local library path.

    I'm not sure yet how to specify a dependency for cmake to check; for now you can use CXXFLAGS/LDLFAGS to specify the location.

    Thanks, Darby

     
  • Kai-Uwe Behrmann

    0.7.3_beta4 failed build log

     
  • Kai-Uwe Behrmann

    Logged In: YES
    user_id=634841
    Originator: YES

    The failing things are not visible. It simply stops.
    Looking in the Makefile does not help. Switching VERBOSE
    to TRUE gives no glue. It is awkward that cmake users
    (this means you) have to do every bit by them self. My build
    log is attached, but is pretty meaningless compared to a
    autotools log.
    fltk-config seems not been found? As well CXXFLAGS seems not
    used for 'make'. How can I switch on more verbosity?
    Possibly a INSTALL text file where you explain, would help me
    cmake new comer or a configure script with proper output as usual.
    File Added: build.log.txt

     
  • Kai-Uwe Behrmann

    Logged In: YES
    user_id=634841
    Originator: YES

    fltk-config is found. Sorry this was my local problem due to too
    many versions on the run. Thanks is works as you wrote.
    Nevertheless, it would sometimes be enlightening to have some
    verbosity for cmake's activities.

     
  • darbyjohnston

    darbyjohnston - 2007-10-10

    Logged In: YES
    user_id=1114113
    Originator: NO

    Thanks for testing it out...

    > Nevertheless, it would sometimes be enlightening to have some
    > verbosity for cmake's activities.

    I'll add some print statements to show what the build variables are set to, that should help a bit with troubleshooting.

    I know cmake isn't as "standard" as autoconf, but I've been really happy with it's simplicity and cross-platform support. Once you get used to it, it's very easy to modify and setup; the more I use it the more I like it. Which is pretty much exactly the opposite of how I feel about autoconf. :)

    Thanks, Darby

     
  • darbyjohnston

    darbyjohnston - 2008-01-25
    • status: open --> closed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks