Trying to understand SDK generation...
From: Henrik (slaskhenrik_at_gmail.com)
Date: 02/25/05
- Next message: Prakash: "Hanging operating system issue"
- Previous message: Jeo: "Re: Nesting interrupts with ARM core"
- Next in thread: Bruce Eitman \(eMVP\): "Re: Trying to understand SDK generation..."
- Reply: Bruce Eitman \(eMVP\): "Re: Trying to understand SDK generation..."
- Messages sorted by: [ date ] [ thread ]
Date: 25 Feb 2005 04:59:12 -0800
After struggling with how to make my features include themselves in the
SDK, Bruce Eitman proposed to add a "makefile.inc" in my projects that
copy the files i want included in the SDK to the SDK's target
directory. This works just fine, but , as allways, I feel I want to dig
deeper into how the whole concept is supposed to work.
For example:
A HW device manufacturer (of say a ISA IO-card) has developed a
CE-driver. I'd imagine he'd like the headers and libs needed to program
applications against his driver to be included in the SDK, if the
customer included the feature in the platform. How does he solve that?
Do you use makefiles and copy commands or are there any ohter
alternatives? I've seen the use of "RELEASETYPE=SDK". What does this do
compared to for example "RELEASETYPE=PLATFORM"? Where can I find more
in-depth info?
Henrik
- Next message: Prakash: "Hanging operating system issue"
- Previous message: Jeo: "Re: Nesting interrupts with ARM core"
- Next in thread: Bruce Eitman \(eMVP\): "Re: Trying to understand SDK generation..."
- Reply: Bruce Eitman \(eMVP\): "Re: Trying to understand SDK generation..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
