- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
On the windows7 PC, the compiler is: 'Invoking: GCC C Compiler 4 [arm-linux-gnueabihf]'
I am trying to use Pth, and I can certainly configure and make it on the de10-nano itself, however the libpth.a file it produces does not work on the windows7 PC build environment. I notice the compiler on the de10-nano itself is: gcc (Linaro GCC 6.2-2016.11) 6.2.1 20161016
I thought I could just copy the libpth.a file and link it - but the build environment cannot find file (even though I tell it where it is) - the error may be that the .a file is not ABI compatible?
So - the cut this short - an example of building a hello world with a library linkage would be ideal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I found the clue here: https://developer.arm.com/docs/100070/latest/image-structure-and-generation/specifying-user-libraries-when-linking
You can use the
--library=name
option to specify static libraries, libname
.a.
So - even though the actual filename is libpth.a - however the build tool only works if I say it is: pth
the tool adds the lib at the front and the .a at the end, and will not countenance the user supplying the full (and valid!) filename!?!?!
good grief.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I should note that hello_world compiles fine and targets down onto the de10-nano - but of course it is only a single source file. How to incorporate big lumps of 3rd party code (such as a static library) is what I am missing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wishing I had stayed with Nios2... 😂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I found the clue here: https://developer.arm.com/docs/100070/latest/image-structure-and-generation/specifying-user-libraries-when-linking
You can use the
--library=name
option to specify static libraries, libname
.a.
So - even though the actual filename is libpth.a - however the build tool only works if I say it is: pth
the tool adds the lib at the front and the .a at the end, and will not countenance the user supplying the full (and valid!) filename!?!?!
good grief.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page