Steve
Mon May 12 17:39:22 PDT 2008
I once wrote an article on how to clone that one on a per platform basis...
I'll dig around my old files and see if I can find it. (It used to be stored
on the EmbeddedFusion site, but that's gone now and I'm not sure if I have
the original anywhere...)
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT
com> wrote in message news:#UK$zFItIHA.3604@TK2MSFTNGP03.phx.gbl...
> Yes, it's building a different version of the library which GWES will link
> with during sysgen. I don't like doing it that way, since it causes the
> public version of the library to be 'damaged', in favor of your version,
> but MS often assumes that you're only targeting one sort of device and
> that, if you screw up those PUBLIC libraries, you won't care.
>
> There are a couple of alternatives:
>
> 1. Keep doing what you're doing (why are you doing this, by the way?
> What's wrong with the default calibration stuff?). In that case, to debug
> why you're not getting the right thing, you need to be sure that your
> clone is getting built, that the output files, resource and object, are
> getting put in the right places in PUBLIC, and that you've done a Sysgen
> to actually build GWES.EXE.
>
> 2. Change the cloned build configuration (set RELEASETYPE to platform in
> the SOURCES file), to build a platform (or project), version of the
> calibrui component, and build GWES.EXE yourself, overwriting the one
> generated by Sysgen. This allows you to avoid messing with the
> Microsoft-provided PUBLIC libraries, at the cost of having to have another
> element of the build, one that builds GWES.EXE. If you decide to go this
> way, you'd need to use sysgen_capture to capture the make instructions for
> GWES (check the help for the sysgen_capture command line. I think you
> need something like 'sysgen_capture -p common gwes', executed from a new
> folder in your platform build structure. This will give you a sources.x
> file or two, one of which you'll rename to SOURCES, and modify to use your
> own CALIBRUI library, rather than the PUBLIC one.
>
> Paul T.
>
> <jigger@hermanhouse.com> wrote in message
> news:3ee55585-4dfe-4ced-befc-b493b60b4679@y38g2000hsy.googlegroups.com...
> On May 12, 5:56 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
> no instrument no spam DOT com> wrote:
>> Are they getting built? Give us a pointer to the instructions you are
>> following, so we can take a look at them. My guess is that things are set
>> up so that the calibrui component, modified by you, is supposed to be
>> built
>> and copied to the flat release folder after the public code sysgen is
>> done,
>> effectively just doing a build and overwriting the output file. If your
>> code never gets built, because you didn't modify one of your DIRS files
>> to
>> add the calibrui cloned component to the build list or something like
>> that,
>> nothing will happen.
>>
>> Paul T.
>>
>
> The instructions are labeled "How to Replace the Calibrui Module" in
> Plaftorm Builder help. In the instructions it sounds like calibrui.obj
> gets built into gews.exe, but I don't get how that works. When I do
> step 5 (check gwes to see if the resources are changed), my changes to
> resources do not show up in gwes. However, I can see that the
> resources are getting compiled into a RES file in the CalibRui project
> folder.
>