U++ forum: Welcome to the forum

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

Mon, 06 October 2014 08:40

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

Ultimate Contributor

Hi Klugier

Klugier wrote on Sun, 05 October 2014 15:09

Hello,

I can not fully understand what is the purpose of file "GCC.bm.in". The first problem I have found is when you copy this file to "~/.upp/theide" the build method will be not detected. At least until the time when you change the name to "GCC.bm". Moreover even "Build methods" (Ide -> Setup -> Build methods..) cannot import this file. It can only works with "GCC.bm". Simply rename do the trick.

Do we need "GCC.bm.in" which is the same file as "GCC.in", but it posses import limitation?

P.S. 1
"GCC.bm" is not included in nightly tarbals. What is interesting here is that makefile can react on succesfull ide build and copy "GCC.bm" to following directory "~/.upp/theide" (Do not override if the file exists!!!). This small change will guarantee that IDE will works out of the box on POSIX.

Files called "*.in" are commonly used in Makefiles and other build systems as templates. They do not contain fully functional content, but they are used as input to the build system, which fills in the missing parts to create full file. This is mostly used to allow different files on different systems, the build system always fill correct values. In this particular case, it takes care of the library paths, which can be different between various Linux distributions.

Klugier wrote on Sun, 05 October 2014 15:09

P.S. 2
IDE should have capability to export certain build method or all methods.

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

Best regards,
Honza

Report message to a moderator