#16 slibtool filters out --target from compile/link flags
Closed 3 years ago by orbea. Opened 3 years ago by orbea.

Original issue: https://github.com/midipix-project/slibtool/issues/9
Opened by: https://github.com/michaelforney

michaelforney commented on May 5, 2017

clang uses the --target flag to specify a cross-compilation target. However, it also looks like slibtool handles --target specially, with the help text set an explicit (cross-)target, then pass it to the compiler.

What does slibtool do with this option? I don't see the target being passed to the compiler.

midipix commented on May 6, 2017

The observation is correct. Currently, slibtool does indeed "set an explicit (cross-)target", but then does not "pass it to the compiler".

I should be able to fix this within the next three days, and will try to attend to this even earlier.

midipix commented on May 6, 2017

It seems to me that a good approach would be the following:

* for a --target argument that precedes the compiler argument, as in: slibtool --target=xxx --mode=compile cc
  --> set an explicit (cross-)target,
  --> but do not pass the argument to the compiler.

* for a --target argument that follows the compiler argument, as in: slibtool --mode=compile cc --target=xxx
  --> set an explicit (cross-)target,
  --> and also pass the argument to the compiler.

Please let me know how that sounds.

michaelforney commented on May 7, 2017

Yeah, that sounds reasonable to me.

midipix commented on May 20, 2017

Thanks for identifying the issue. Fixed according to the above in commit 288d628.

midipix commented on Aug 4, 2017

Fixed in commit 288d628, reported on irc by multiple users to be working.

midipix closed this on Aug 4, 2017


Metadata Update from @orbea:
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata