I would like to create a custom Package that makes it simple for developers to create new projects targetted at a specific hardware platform, so that they can simply click on the appropriate choice in the new project wizard.
I have read the online help about mkpkg and set up a combining project which does produce a valid package file. But this doesn't actually seem to be doing anything very useful. Do you have any more detailed information about what I need to do?
Essentially, there are only a few settings which my new project template needs to provide as standard:
- set the basic target CPU type
- preset the User Include dir
- preset some pre-processor defines
- set an additional linker option flag
- set the EntryPoint
- set a linker script file as a System file
- set a library file as a System file
- set a post-link command line
I have created a package that references the four files I need:
- the xxx_package.xml file
- a project_templates.xml file
- the linker script file
- the library file
However, I get several problems:
- when I try to install this package manually, it complains that it depends on an Intel XScale package being loaded
- when I create a new project referencing my new package, the tab showing System files tab is empty, and I don't get the usual hierarchy in Project Exporer of Project Properties, Source Files and System Files. Also none of the settings from the Package has been applied to the new project.
I am sure that for someone who knows their way around the internals of CrossWorks, it is very easy to do what I want. But it is non-trivial to work that out from the online documentation....
I attach a zip file with my output package file and the four files that go into it.
Please sign in to leave a comment.