This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See crosstool-NG for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Howto implement a second newlib variant


Hi!

I would like to add an additional build step for a second newlib variant
called newlib-nano. It requires the exact same build step as the normal newlib
(configure, make, make install), but uses different configure options.
The result is then:
  libc_nano.a
  libg_nano.a
  librdimon_nano.a
  libstdc++_nano.a
  libsupc++_nano.a
All of this libs are generated for each multilib variant.

As I understand how CT_NG works, I have to add a new build step, because it is
a complete new configure, make, make install triple, which could fail and needs
to be restarted (step).

So I have to add the new step (libc_nano) to steps.mk and implement it in
newlib.sh.

I could add the second build to the libc step in newlib.sh, but then there is
no separate build directory for it and I can't reuse all the nice features from
the top level script (create the build directory, rebuild a step, ...).

Or is there another possibility?

BR
   Jasmin

--
For unsubscribe information see http://sourceware.org/lists.html#faq


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]