|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ View Advanced ]
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Reproducibility |
Date Submitted |
Last Update |
|
0000152 |
[cparser] compiler driver |
major |
N/A |
2015-05-04 20:38 |
2015-05-04 20:38 |
|
|
Reporter |
Matze |
View Status |
public |
|
|
Assigned To |
|
|
Priority |
high |
Resolution |
open |
|
|
Status |
new |
|
Product Version |
|
|
|
Summary |
0000152: Define a scheme to find libc+compiler headers and libraries |
|
Description |
The compiler needs to find the headers of the compiler, the system libc and the libc probably needs to include system specific headers.
We already have heuristics in place that work for the common case of targetting the host machine. However we should define and document a scheme on how to find these paths when cross compiling.
While this is easy to change in the compiler in src/driver/c_driver.c append_include_paths() the main task here would be to document the desired behaviour and in practice see where we actually do get libraries and headers from that adhere to the scheme.
One scheme I could imagine when targetting TARGET would be to use /usr/include/TARGET and /usr/lib/TARGET, alternatively maybe /opt/TARGET/libc/include and /opt/TARGET/libc/lib where /opt/TARGET/libc being a default that can be changed with a commandline flag.
We also have to see whether we need to use a target specific linker and where to find that, and which libraries need to be linked by default for a given libc. |
|
Additional Information |
|
| Tags |
No tags attached. |
|
|
Attached Files |
|
|
|
Relationships 
