[Gambas-devel] Fwd: What about cmake?

Sebastian Kulesz sebikul at ...176...
Wed Nov 13 20:25:17 CET 2013


---------- Forwarded message ----------
From: Benoît Minisini <gambas at ...1...>
Date: Wed, Nov 13, 2013 at 4:09 PM
Subject: Re: [Gambas-devel] What about cmake?
To: Sebastian Kulesz <sebikul at ...176...>


Le 13/11/2013 19:21, Sebastian Kulesz a écrit :

>
>
>
> On Sat, Nov 9, 2013 at 6:54 PM, Benoît Minisini
> <gambas at ...1... <mailto:gambas at ...1...>>
> wrote:
>
>     Le 31/10/2013 22:37, Sebastian Kulesz a écrit :
>
>         After a lot of struggle i managed to create a somewhat generic
>         set of
>         macros to build and install the needed components. Although the
>         runtime
>         installs just fine, i'm having trouble when running the Gambas
>         informer
>         to create the .info files. I tried reading the gbi.c file but found
>         nothing wrong with components are installed.
>
>
>     gbi3 shoud be run during installation time as root, after *each*
>     installation of a component.
>
>     Why? Because some components are Gambas projects that must be
>     compiled, and so they need the information files of other components.
>
>     Moreover, you must follow the compilation order defined in the
>     'comp/src/order' file for these Gambas-only components.
>
>
>
>         There is one difference
>         with the autoconf setup though; libtool is not supported by
>         cmake, so
>         gcc is called directly, not through the libtool file.
>         I'm think this last point might be the problem. If it is, is
>         there any
>         fix, or is libtool absolutely necessary?
>
>
>     I don't know. As I explained in another mail, Gambas shared-library
>     are not system libraries, but just extension to the interpreter.
>     Only the *.so file is needed. So there is a good luck for libtool
>     not to be needed.
>
>
> Then i'm doing it right. But still, for some reason, gbi3 can't find the
> component's .so files. If the .la file is present, it tries to load it,
> but as it is not a binary file it will fail (not sure why it is trying
> to load a text file).
>

Normally it should use only the *.so file. Where do you see that it tries
to load the "*.la" files?



> Do i need to install the .la files or can i just skip them? Are they
> needed by the informer o any other component?
>

Normally they are used only if a program uses the libtool library
(lt_dlopen in the source code).

Are there any side effects if i compile Gambas with libtool disabled by
default? Maybe that's the problem. At least to get it to work, i will look
into that later once the project can be installed and executed.



> Aside from that, the binary build system is finished (will do the Gambas
> one once i can install and run the interpreter). I still need to add
> some checks for a few components, but that can be done later.
>
> I won't have time to continue this work until December at least as
> finals are really close. If someone would like to continue, please let
> me know so that i can provide a tarball with the latest source.
>
>
Ask that on the mailing-list then. If you can claim big speed-up in
configuration time, maybe some people will help you! :-)

Well, i thought i was talking in the mailing list. Gmail defaults to reply
instead of reply to all. :P

The speedups are incredible. Full tree, less than 30 seconds for a full
configure, reconf is long gone now. It has some other advantages, like
building components out of the source tree. You can build distribution
packages right there, without knowing anything about packaging. Also,
compilation is a little bit faster, as gcc is invoked directly and not
through a wrapper script, and there is not much directory movement.

So, if you want to help let me know. Besides, cmake is really interesting
to learn.

Regards,

-- 
Benoît Minisini
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gambas-basic.org/pipermail/devel/attachments/20131113/53252883/attachment.html>


More information about the Devel mailing list