Separate x86 targets in one platform

Greetings!

Just up front, I don't know if I really do have a problem yet, but I have
some concerns which I'd like to discuss.

So, what I'm concerned about is this: we have a platform that will be
deployed to two different x86-based (plus one MIPS and ARM Emulator)
machines. For each of the x86-based machines I have to make some
adjustments, add special drivers etc. AFAICT (and here is the part I
haven't tried yet), I can't simply throw everything into the same platform.
While this works for the MIPS and ARM drivers, which are sufficiently
separate from the others, I would end up with at best unnecessary drivers
and at worst with conflicting drivers.

What I thought of were these remedies:
1. Create separate configurations
Instead of having only debug and release, I would have debug_variant1,
debug_variant2 and similar for release. This of course wouldn't apply to
the non-x86 variants where these would be the same.
2. Separate the second x86 platform from the rest
That would mean that I have to manually sync the two resulting platforms. If
I could, I'd rather avoid that.

Suggestions?

thanks

Uli

Valter
Mon Feb 05 05:39:24 CST 2007

Ulrich Eckhardt <eckhardt@satorlaser.com> wrote in
news:9fcj94-5ig.ln1@satorlaser.homedns.org:

[...]
> So, what I'm concerned about is this: we have a platform that will
> be deployed to two different x86-based (plus one MIPS and ARM
> Emulator) machines. For each of the x86-based machines I have to
> make some adjustments, add special drivers etc. AFAICT (and here
> is the part I haven't tried yet), I can't simply throw everything
> into the same platform. While this works for the MIPS and ARM
> drivers, which are sufficiently separate from the others, I would
> end up with at best unnecessary drivers and at worst with
> conflicting drivers.
[...]
> Suggestions?

You can clone the CEPC BSP (or the reference BSP you used) for each of
the x86 based boards and add the SYSGENs for the specific drivers on
their <platformname>.bat files.
In this way you'll have a different build environment for each target.
If you need some shared files or registry key you may add an empty
project with the required .bib and .reg entries or #include a common
.reg and a .bib from the different project.* files in your workspace.

--
Valter Minute
(the reply address of this message is invalid)
(l'indirizzo di reply di questo messaggio non è valido)