Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 8463] Build system selection

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT bugs.sourcemage.org
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 8463] Build system selection
  • Date: Sat, 24 Sep 2005 10:16:39 -0700 (PDT)

http://bugs.sourcemage.org/show_bug.cgi?id=8463





------- Additional Comments From acedit AT armory.com 2005-09-24 10:16 -------
(In reply to comment #3)
> I'd do CONFIGURE_CMD and MAKE_CMD instead of a BUILD_CMD.
> Why? To reduce doubling of the code.

You could do this on your end:
BUILD_CMD="autotools_configure && jam_build"

Also, CONFIGURE_CMD would confuse itself with overriding the CONFIGURE file
that
runs before DEPENDS.

>
> jam based systems still use ./configure with the same options
> so basicaly having an autotools_configure, scons_configure,
> jam_build, make_build, scons_build Would be nice.
>
> Like the DETAILS idea... I think I was discussing that one on irc
> with somebody though and someone mentioned that we don't want more
> vars in DETAILS.
>
> I accually like it to be settable in DETAILS. One less file to have
> in the spell.

Exactly. You're going to have to have the info _somewhere_, so either theres a
file with a single line in it, or a line in DETAILS doing the same thing at
much
less cost. If someone doesnt want more lines in their spell's DETAILS file
they
can add a file. Its up to them how they want to do it since the same functions
available to the *_CMD vars are accessible in the spell files.


--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.




Archive powered by MHonArc 2.6.24.

Top of Page