Re: Trying to understand SDK generation...
From: Bruce Eitman \(eMVP\) (beitmannospam_at_NOSPAM_applieddata.NOSPAM_net)
Date: 02/27/05
- Previous message: Bruce Eitman \(eMVP\): "Re: Power On/OFF Issue ?"
- In reply to: Henrik: "Trying to understand SDK generation..."
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 27 Feb 2005 11:55:49 -0500
Try looking at Common\Oak\Misc\Makefile.def.
RELEASETYPE=SDK works for your lib, DLL and exe. But does not put the
header file in the SDK, which is what you asked about in your OP. But, note
that if you change to SDK, you may need to change other sources files to
look for the lib files there.
-- Bruce Eitman (eMVP) Senior Engineer beitman AT applieddata DOT net Applied Data Systems www.applieddata.net An ISO 9001:2000 Registered Company Microsoft WEP Gold-level Member "Henrik" <slaskhenrik@gmail.com> wrote in message news:1109336352.075954.84620@f14g2000cwb.googlegroups.com... > 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 >
- Previous message: Bruce Eitman \(eMVP\): "Re: Power On/OFF Issue ?"
- In reply to: Henrik: "Trying to understand SDK generation..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|