[openbeos] Re: haiku.image with developer tools and co
- From: Dane Scott - TuneTracker Systems <dane@xxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Fri, 28 Mar 2008 09:46:30 -0500
This is a consumer-oriented guy talking here, so if I'm missing
something, it's ok to explain it to me. But why can't the optional
packages just include built binaries? It doesn't add all *that* much to
the download, and then they're ready to rock...without the need for a
Linux'ey auto-build system on the user's PC.
--
Ingo Weinhold wrote:
On 2008-03-28 at 17:59:01 [+0100], Ralf Schuelke <teammaui@xxxxxx> wrote:
i build a image with:
jam haiku-image
but we can add the developer tools into the image?
gcc,headers,pe, etc...
and i listen the pe editor is the default coding editor, is this in the
haiku tree now ? ore used from pe@berlios ?
Haiku's build system has a feature called optional packages, which will
include additional software. Most of them will download one or more zip
files from the internet (via wget). You can enable the optional packages
you want in your build/jam/UserBuildConfig file, e.g.:
AddOptionalHaikuImagePackages Development Pe ;
the other is, beos have a nice makefile engine, have haiku gcc this too ?
(a jamfile-engine for apps are nice too :-) )
We don't have a makefile engine yet. I suppose we want one, though.
CU, Ingo
- Follow-Ups:
- [openbeos] Re: haiku.image with developer tools and co
- From: Bruno Albuquerque
- References:
- [openbeos] haiku.image with developer tools and co
- From: Ralf Schuelke
- [openbeos] Re: haiku.image with developer tools and co
- From: Ingo Weinhold
Other related posts:
- » [openbeos] haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
- » [openbeos] Re: haiku.image with developer tools and co
On 2008-03-28 at 17:59:01 [+0100], Ralf Schuelke <teammaui@xxxxxx> wrote:
i build a image with:jam haiku-imagebut we can add the developer tools into the image? gcc,headers,pe, etc... and i listen the pe editor is the default coding editor, is this in the haiku tree now ? ore used from pe@berlios ?
Haiku's build system has a feature called optional packages, which will include additional software. Most of them will download one or more zip files from the internet (via wget). You can enable the optional packages you want in your build/jam/UserBuildConfig file, e.g.:
AddOptionalHaikuImagePackages Development Pe ;
the other is, beos have a nice makefile engine, have haiku gcc this too ? (a jamfile-engine for apps are nice too :-) )
We don't have a makefile engine yet. I suppose we want one, though. CU, Ingo
- [openbeos] Re: haiku.image with developer tools and co
- From: Bruno Albuquerque
- [openbeos] haiku.image with developer tools and co
- From: Ralf Schuelke
- [openbeos] Re: haiku.image with developer tools and co
- From: Ingo Weinhold