[prev in list] [next in list] [prev in thread] [next in thread] 

List:       leaf-devel
Subject:    Re: [leaf-devel] Problem compiling
From:       KP Kirchdoerfer <kapeka () users ! sourceforge ! net>
Date:       2013-02-18 18:43:58
Message-ID: 5122766E.60604 () users ! sourceforge ! net
[Download RAW message or body]

Hi;

Am 18.02.2013 19:04, schrieb Hervé Delmas:
> Thank you for the answer :-)
> 
> Yes I have downloaded and compiled the Bering uClibc 5.x. 
> 
> I am using ubuntu 12.04LTS and the 5.x toolchain compiled like a charm.

Great - (btw: you'll won't have any benefit of a VM appliance from now
on :))

> The thing that stop me before it is because I don't catch where to work.
> For example,  I have tried to touch dnsmasq-2.63.tar.gz in the "repo" or
> in "source" and I have tried to touch "*.c" in  "dnsmasq-2.63/src", but
> every times I tried to rebuild the package, nothing compile.
> 
> 
>         ./buildtool.pl build dnsmasq
>         make the list of required source packages:  nothing to do [0.K.]
>         make the list of required build packages:  nothing to do [0.K.]
>         

Yep; we are working with a debian-like approach: apply patches to a
source first and compile thereafter.

Create a patch for your changes to dnsmasq.c (or whatever)  - look for
examples in the shorewall repo,
add the patch file in dnsmasq/buildtool.cfg (<file> declarations) and
apply the patch in dnsmasq/buildtool.mk (again see
shorewall/buildtool.mk for an example)

Also have a look with ls -al into repo/dnsmasq and soure/i486.../dnsmasq
to see how we use linked files in our buildenv.
Rule of thumb: new files have to go to repo/[package]...

hth
kp

> Do I have to run ./buildtool.pl srcclean evrytimes to force compilation
> after source modifications?
> 
> 
> 
> -----Original Message-----
> From: KP Kirchdoerfer <kapeka@users.sourceforge.net>
> Reply-to: kapeka@users.sourceforge.net
> To: leaf-devel@lists.sourceforge.net
> Subject: Re: [leaf-devel] Problem compiling
> Date: Mon, 18 Feb 2013 15:53:11 +0100
> 
> 
> Am 18.02.2013 00:23, schrieb Hervé Delmas:
>> Hi everybody, 
>> 
>> I would like to compile a small program for my Bering Uclibc 4.3.  I
>> read the Developer Guide but I am not sure I get it.  I tried to modify
>> an existing package locally on my computer, but the buildtool seems to
>> compare the source on the git repository. Is there a way to compile
>> source locally modified on my computer?
>> 
>> Is there an "hello world" program that I can use to start?
> 
> No;
> 
> I assume you have downloaded and extracted the complete sources tarball
> (e.g. Bering-uClibc_4.3.3_src.tgz)
> 
> Next run
> ./buildtool.pl build buildenv (or build toolchain for 5.x)
> 
> If that doesn't work you either do have all required host files/apps or
> it isn't working as we expected (note: the 5.x toolchain improved a lot
> to be "self-hosted").
> 
> Modify repo/packagename/buildtool.cfg and buildtool.mk to fit your
> needs, you also need the new source package in that directory, or
> declare a new file if you just want to add patch.
> 
> Next run ./buildtool.pl build packagename
> if it fails, look at log/buildtool.log change the buildtool.cfg|mk and do a
> ./buildtool.pl srcclean packagename before running the build again.
> 
> A "hello world" program will soon be cluttered if we try to explain
> everything; a good start will be an "easy" package like dnsmasq.
> 
> 
>> Is there an easier way to have a developing  environment. I am thinking
>> to something I can run native in a virtual machine for examples (like in
>> virtualBox).
> 
> I do have one, but it just free's you of step one (build buildenv) and
> is a lot slower (6hrs for a complete build compared to 2hrs)
> 
> Maybe we can give more help, if you are more specfic (package,
> buildtool.* and buildtoollog snippet).
> 
> kp
> 
> ------------------------------------------------------------------------------
> The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
> is your hub for all things parallel software development, from weekly thought 
> leadership blogs to news, videos, case studies, tutorials, tech docs, 
> whitepapers, evaluation guides, and opinion stories. Check out the most 
> recent posts - join the conversation now. http://goparallel.sourceforge.net/
> 
> _______________________________________________
> leaf-devel mailing list
> leaf-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/leaf-devel
> 
> 
> 
> ------------------------------------------------------------------------------
> The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
> is your hub for all things parallel software development, from weekly thought 
> leadership blogs to news, videos, case studies, tutorials, tech docs, 
> whitepapers, evaluation guides, and opinion stories. Check out the most 
> recent posts - join the conversation now. http://goparallel.sourceforge.net/
> 
> _______________________________________________
> leaf-devel mailing list
> leaf-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/leaf-devel
> 

------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

[prev in list] [next in list] [prev in thread] [next in thread]