[Gambas-devel] What about cmake?

[Tobias Boege]

On Sun, 13 Oct 2013, Sebastian Kulesz wrote:
> ---------- Forwarded message ----------
> From: "Sebastian Kulesz" <sebikul at ...176...>
> Date: Oct 13, 2013 1:03 PM
> Subject: Re: [Gambas-devel] What about cmake?
> To: "Beno?t Minisini" <gambas at ...1...>
> Cc:
> 
> Here [0] is an updated package (not up to date with trunk). Most of the
> tree is now ported to cmake, i'm missing a few components which i had some
> trouble building or finding the libraries they depend on. The code is much
> cleaner now, i removed A LOT of files and symlinks. Cmake simplified a lot
> the include directives.
> 
> I need some info about the installation process for the binary components.
> If possible, the exact steps autoconf executes when doing a make install in
> every component.
> 
> I'm also having a build error with gbx about an existing symbol with a
> different declaration which is causing an error.
> 
> I had to move, remove and change a lot of files. Please test it in your
> system an let me know if you find a bug. As before, installation is not yet
> implemented.
> 
> Hope you mine it!
> 
> [0] http://goo.gl/1rBMhS

I just tested it. Apart from a compilation error in gb.db.postgresql (this
may not have anything to do with your changes), the configuration process
does not run properly if the SVN revision cannot be found (because SVN fails
when cmake tries to use it to get the revision number).

The archive is called "-nosvn" but the configuration simply dropped out with
an error until I copy the .svn directory from my real working copy to your
gambas3-cmake-nosvn directory. Then it worked. It's not supposed to work
this way, right? Maybe you are developing the cmake port above an svn
checkout and didn't notice this therefore?

If you ask, I'll probably provide the information tomorrow. (I'll maybe have
a look at the postgresql thing, too, as in the normal trunk/, there is no
problem with postgresql, the component builds and installs just fine. The
error is about a missing include, so it _may_ be related to cmake's way of
detecting the include directory but I have no time to look at it today.)

Regards,
Tobi

-- 
"There's an old saying: Don't change anything... ever!" -- Mr. Monk