U++ forum: Welcome to the forum

Re: What is the purpose of "GCC.bm.in" in tarbals? [message #43766 is a reply to message #43764]

Tue, 07 October 2014 06:27

dolik.rce
Messages: 1789
Registered: August 2008
Location: Czech Republic

Ultimate Contributor

Klugier wrote on Mon, 06 October 2014 18:57

The main problem with "GCC.bm.in" is that it cannot be used as build method. Moreover tarbal dosen't offer any build method (.bm file), so after successful compilation, ide cannot compile any application. This is huge drawback, because you will need to configure ide that you dosen't know.

It is not intended to be used as build method. It is only template, the actual build method is created when building TheIDE.

Klugier wrote on Mon, 06 October 2014 18:57

Like I sad before we can copy "GCC.bm" to "~/.upp/ide" after build and then user can use ide out of the box.

GCC.bm is installed automatically, when you call either "make install" or the "doinstall" script directly.

Klugier wrote on Mon, 06 October 2014 18:57

GCC.bm IS THE SAME FILE AS GCC.bm.in !!!

No, it is not. The GCC.bm.in contains placeholder "((INCLUDES))". This string is replaced by "domake" script, to create actuall GCC.bm, using this exact code:

if which pkg-config
then
	sed -e "s@-I((INCLUDES))@`pkg-config --cflags-only-I gtk+-2.0`@g" uppsrc/Makefile.in >uppsrc/Makefile
	sed -e "s@((INCLUDES))@`pkg-config --cflags-only-I gtk+-2.0|sed -e s/-I//g -e \"s/ /;/g\"`@g" GCC.bm.in >GCC.bm
else
	sed -e "s@((INCLUDES))@@g" uppsrc/Makefile.in >uppsrc/Makefile
	sed -e "s@((INCLUDES))@@g" GCC.bm.in >GCC.bm
fi

That means, that if there is pkg-config installed on the target machine, it will be used to determine correct include paths for gtk+-2.0, which is known to vary between its versions.

Klugier wrote on Mon, 06 October 2014 18:57

Quote:

Why? It seems perfectly fine for me to just copy the file *.bm from ~/.upp/ide if I need it to move somewhere else. It is actually simpler then exporting it, because I don't have to start TheIDE first Smile

Fine, but new user dosen't know where ide stores its build methods. Moreover "~/.upp/ide" is hard to find. I have discovered this directory after one year of using Upp. So the idea of adding export beside import option seems to be reasonable.

I'm not saying I'm strictly opposed to the idea. Just that it seems redundant to me. It could be also fixed by providing better documentation. Actually, it is even documented in the Getting started with TheIDE article, there is only slight mistake in the directory path.

Honza

Report message to a moderator