- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Bob
Now permanently having the "Small Window", nothing helps, any suggestions?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is a naming problem. Specifiying a library name results in Creator appending the option '-lLibrary01' to the linker command line. Gcc then interprets this as looking for a file named 'libLibrary01.a' to be loaded.
So either you need to have an additional step renaming the created library file (since I found no place where I could specifiy its name). Or you rename the library project to be called 'libLibrary01'. I did the latter, and it worked.
But why don't you want to specify the dependency to your library project? I see no downside to this...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That was exactly my question: where can I set my library to produce m0 code. Furthermore: When I want to create a library with target independent code (a function that SHOULD work) how to specify that?
Bob>br>Now having permanently the small window, thinking about to quit this forum!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We could always start directing people to psocdeveloper.com, where
these problems with forum software do not exist. Almost a year now to
fix this.........
Regards, Dana.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I justed tested it. If have a test workspace with a PSoC4 and a PSoC5 project in it. I created a new project ("Library01") there, and choose "library project" as type (the "other" tab in the wizard).
Then I opened the project properties for the two other projects, opened end editor for "dependencies" and checked the "code" column for the"Library01"ry project (though it doesn't seem to stick sometimes, better to check again).
When I now build these two projects, the library gets build too, with the CPU settings of the importing project (so I have two different versions of the Library01.a file).
If I compile the library project on its own, it always use the build settings defined for it (which happens to be Cortex-M3 by default, but can be changed).
So maybe you are just missing the dependency setting?
(btw: one also needs to set the proper include path, this won't bet set by adding the dependency)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@bob - no, no shadows, just two weeks at a north sea beach with my family 🙂 And I prefer to stay offline then...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, the "Other Forum"... The software works, but the visits of users is too few (No posts in the last 2 days) I suggested Cypress to use their (free, open) software and adapt it to their needs. Xes, more than a year ago...
So to reduce my blood-pressure it might be the only choice for me to stop contributing here...
Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You know, You can resize that edit window by dragging its bottom-right corner...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think you need to also set the library path. Otherwise gcc will look only in its current directories, but your library is elsewhere.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Of course I provided an additional directory for the library.
Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The lower right corner can be used to expand and reduce the edit box.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is a naming problem. Specifiying a library name results in Creator appending the option '-lLibrary01' to the linker command line. Gcc then interprets this as looking for a file named 'libLibrary01.a' to be loaded.
So either you need to have an additional step renaming the created library file (since I found no place where I could specifiy its name). Or you rename the library project to be called 'libLibrary01'. I did the latter, and it worked.
But why don't you want to specify the dependency to your library project? I see no downside to this...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There was a question from a user in this forum as how to give away a developed functionality without giving away the sources. While testing the howtos I ran into the above problems.
Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Hli
Thanx a lot: The "Lib"-trick indeed did work!
Bob