Replacing COMMON Components by customized ones
From: Yannick Chamming's [eMVP] (ychammings_nospam_at_adeset.com)
Date: 05/18/04
- Next message: Ayman: "Re: Replacing COMMON Components by customized ones"
- Previous message: Ayman: "IESample in 4.2"
- Next in thread: Ayman: "Re: Replacing COMMON Components by customized ones"
- Reply: Ayman: "Re: Replacing COMMON Components by customized ones"
- Reply: Dean Ramsier: "Re: Replacing COMMON Components by customized ones"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 18 May 2004 19:29:17 +0200
Hi all,
I have a "what is the right way" question :
We are willing to replace the intlp.cpl by our own version, linked to a
catalog component of our BSP.
We duplicate the intl sources into our platform directory, make the
adaptation, name it as intlp_mine.cpl, include it in our bib file and
everything works just fine...
... except that we have now 2 intl cpl (standard one and customized one)
How can we remove automatically the standard intl when including ours ?
- If we just rename our cpl in the platform.bib file to name it intlp.cpl we
encounter the well known "duplicate entry", and as wceshellfe.bib is parsed
before platform.bib, it's the standard component which is included.
- We can patch the cesysgen.bat file to add an env variable around the
standard component, and set the env variable when including our customized
version, but as the cesysgen.bat is project specific file, this modification
will be either dedicated to a CE project, or to all CE projects on a
specific PB install (if we modify the template cesysgen), but we won't be
able to export it with our BSP to other PB installs
- We can just modify the original version into public... so ugly ! And still
the issues when exporting our BSP.
- The only automated way we found to make it work is to include our
component in config.bib under the intlp.cpl : we still have the duplicate
entry issue, but as it is the first file parsed by PB, it is ours which is
included, not the standard one from wceshellfe.bib
A google search highlighted a similar question from Paul G.Tobey one year
ago, but he did'nt seem to receive a pertinent answer.
We were thinking of a kind of "Bib record remover" (a bit like
the -[HKLM\...] of the reg file, but for bib files) : we could use it to
remove the standard intlp record before adding ours...
Any hints ?
Best regards
Yannick
-- ---------------------------------------------------------------- Yannick Chamming's (eMVP) ADESET Windows Embedded Manager ychammings AT adeset DOT com> http://www.adeset.com Tél : +33 (0)4.72.18.57.77 Fax : +33 (0)4.72.18.57.78 ----------------------------------------------------------------
- Next message: Ayman: "Re: Replacing COMMON Components by customized ones"
- Previous message: Ayman: "IESample in 4.2"
- Next in thread: Ayman: "Re: Replacing COMMON Components by customized ones"
- Reply: Ayman: "Re: Replacing COMMON Components by customized ones"
- Reply: Dean Ramsier: "Re: Replacing COMMON Components by customized ones"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|