U++ forum: Welcome to the forum

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

Mon, 06 October 2014 18:57

Klugier
Messages: 1076
Registered: September 2012
Location: Poland, Kraków

Senior Contributor

Hello dolik.rce,

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.

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 THE SAME FILE AS GCC.bm.in !!!

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.

Sincerely,
Klugier

U++ - one framework to rule them all.

[Updated on: Mon, 06 October 2014 20:34]

Report message to a moderator