Closed Bug 493609 Opened 15 years ago Closed 14 years ago

add make building for builtins for ease of building in artifact clean branches

Categories

(Tamarin Graveyard :: Build Config, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Future

People

(Reporter: treilly, Unassigned)

Details

Attachments

(1 file)

No description provided.
Attachment #378103 - Flags: review?(stejohns)
Attachment #378103 - Flags: review?(stejohns) → review+
Comment on attachment 378103 [details] [diff] [review] make rules for builtins we should leave this open, because: -- we should offer a way to move the files out of core, as that's problematic for Flash -- would be nice to add similar build rules for win & mac IDEs someday
Component: Garbage Collection (mmGC) → Build Config
OS: Mac OS X → All
QA Contact: gc → build-config
Hardware: x86 → All
Target Milestone: --- → Future
Assignee: treilly → nobody
+1 we should have no generated files in hg IMHO
(In reply to comment #3) > +1 we should have no generated files in hg IMHO I disagree somewhat, it is beneficial to be able to build Tamarin on platforms that have a C compiler without requiring Java SE 1.5+ to be present as well in order to run ASC. (After all we have eval :-) Thus the ABCs should be in the Tamarin tree.
(In reply to comment #4) > I disagree somewhat, it is beneficial to be able to build Tamarin on platforms > that have a C compiler without requiring Java SE 1.5+ to be present as well in > order to run ASC. (After all we have eval :-) Thus the ABCs should be in the > Tamarin tree. We already have (effectively) a requirement for Python to build, due to nativegen.py. Adding Java doesn't seem like that heinous a requirement.
(In reply to comment #5) > (In reply to comment #4) > > I disagree somewhat, it is beneficial to be able to build Tamarin on platforms > > that have a C compiler without requiring Java SE 1.5+ to be present as well in > > order to run ASC. (After all we have eval :-) Thus the ABCs should be in the > > Tamarin tree. > > We already have (effectively) a requirement for Python to build, due to > nativegen.py. Adding Java doesn't seem like that heinous a requirement. The nativegen.py requirement assumes your conclusion. I'm saying that it would be good to be able to check out a tree and build it with a C++ compiler. If the build does not need to run nativegen.py, which is what I'm suggesting, then python won't be required, I think.
This bug was fixed but was left open for bogus scope creep reasons, closing.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: