MSDN-2540

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hello,

recently I've followed the MSDN-2540 course, but some things are not
quite clear to me
(better said: it has invoked more questions than answered them)

The codebase software of our device has following structure under PB
5.0:

$(_WINCEROOT)\PLATFORM\DEVICE_X\SRC\BOOTLOADER
$(_WINCEROOT)\PLATFORM\DEVICE_X\SRC\KERNEL
$(_WINCEROOT)\PLATFORM\DEVICE_X\SRC\DRIVERS
$(_WINCEROOT)\PUBLIC\DEVICE_X\OAK\DRIVERS
$(_WINCEROOT)\PUBLIC\DEVICE_X\SDK\SAMPLES

The bootloader, kernel and drivers (from platform + public) are to be
shipped to
the customer in binary form, allowing a third party OEM to dynamically
add/remove
functionality and modules with our BSP. The samples are to be shipped
to the customer
as source code.

Question concerning this framework:

1) Is there a wizard that would create a BSP ? I don't mean cloning a
BSP, but an application
that would create an installer package (.msi)?

2) How can we impose the rule of shipping software to the customer in
source/binary form? Do we need to put everything which is
non-sourcecode into a PRIVATE folder (as in MSDN-2540)?

3) Folder $(_WINCEROOT)\PUBLIC\DEVICE_X\OAK\DRIVERS contains all
drivers which should be in our SDK. Folder
$(_WINCEROOT)\PLATFORM\DEVICE_X\SRC\DRIVERS also contains drivers, but
these can be controlled through the standard CE interface. As they
don't have a custom API, they don't need to be shipped in a SDK. Was
this a good reason for splitting the drivers into two directories?

4) In MSDN-2540, we can see a DLL being created in two phases
(presysgen=compile, and sysgen=link), through the cebasesysgenbat.bat
and makefile files. Do I need to do this for all DLLs, i.e. must i
never create a directory under ...\DRIVERS with a sources file
containing SOURCES=DYNLINK? And what about the ...\SAMPLES
applications, can I put there SOURCES=PROGRAM, or must I also firstly
create a library, and link during the SYSGEN phase?

Hopefully someone can shed a light on these cases.

Thank you in advance,

Wesley

.

Relevant Pages

  • Re: MSDN-2540
    ... BSP, but an application that would create an installer package? ... non-sourcecode into a PRIVATE folder? ... drivers which should be in our SDK. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: The 1% are the very best destroyers of wealth the world has ever seen Our common treasury in the
    ... I had to reinstall the ... the ethernet drivers was missing, ... I don't know how that folder got deleted. ... hate hate hate hate hate hate hate working on ...
    (soc.retirement)
  • Re: hp recovery dvd
    ... target customers, because doing so would increase the final cost of a system ... The consequence is that the owner of the computer, your target customer, would ... After that one needs the drivers, ... he/she needs to depend on a service provider to do the job. ...
    (comp.sys.hp.hardware)
  • Re: hp recovery dvd
    ... > would emphasize this for its target customers, ... > customer needs a foolproof way to create them or to order them cheaply ... > creating restore media is not foolproof, and many people do not do so. ... After that one needs the drivers, ...
    (comp.sys.hp.hardware)
  • Re: Android vs Qt vs C/C++
    ... Is it feasible to to port Linux for Android. ... Just heard that the client is going with Freescale MCF5445x micro. ... write the kernel drivers for Accelerometer, GPS, Camera etc? ... A BSP is a _board_ support package. ...
    (comp.arch.embedded)