Opened 17 years ago
Last modified 16 years ago
#1739 closed enhancement
Include a build system script to generate a proper 'develop' directory on Haiku — at Version 7
| Reported by: | nielx | Owned by: | bonefish |
|---|---|---|---|
| Priority: | blocker | Milestone: | R1/alpha1 |
| Component: | Build System | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | zooey, andreasf, scottmc, briandabrain@… | |
| Blocked By: | Blocking: | ||
| Platform: | x86 |
Description (last modified by )
The build system should have support for creating a working development environment on Haiku.
This means creating a '/boot/develop/' structure and including a working GCC 2.95.3 in that.
It might also mean installing the Makefile engine that is used by a lot of projects, but that's open for interpretation.
Change History (9)
by , 17 years ago
| Attachment: | build_developer_tools.sh added |
|---|
by , 17 years ago
| Attachment: | legacy-gcc-haiku-compile-fix.diff added |
|---|
Fix for building the legacy gcc compiler for haiku
comment:1 by , 17 years ago
Adding one note: the gcc patches do not break creating a cross-compiler on linux.
comment:2 by , 17 years ago
Some more poking around. Building a native gcc 4.1.2 with a cross-compiler fails because the cross-linker accepts undefined symbols in applications. This should only happen in shared libraries (and perhaps static). Does anybody know where to look to to change this behavior? Thanks!
comment:3 by , 17 years ago
Another update. I managed to get configure to work correctly by passing the '-z defs' option, which is passed on to the linker. How do i put this in the specs?
comment:4 by , 17 years ago
| Priority: | normal → blocker |
|---|
Making this a blocker. Even though my script might not make it, this ticket can be used as an umbrella for everything needed to build haiku on haiku.
comment:5 by , 17 years ago
Actually, I prefer one ticket per issue. I get confused by tickets which mention multiple different types of issues. Sometimes even comments introduce new (sometimes related sometimes not really related) issues. Then you can't close a ticket without reading all the comments first to see if something would be missed. That's why a prefer one ticked per distinct, precise issue.
comment:6 by , 17 years ago
I agree with Stephan.
The only thing still missing is a downloadable zip file containing a native gcc, BTW. I intend to create one when I actually get around to finishing the tool chain port.
comment:7 by , 17 years ago
| Description: | modified (diff) |
|---|
Well, I agree too, and the summary of this tickets states that the issue is to create a setting in the build system that creates a proper working develop directory. I updated the description to match the summary. Consider this ticket as a step in the self-hosting requirement.
Build script for the legacy gcc