PB catalogue viewer doesn't know how to deal with #include in your

PB scans .bib files to determine if the requirements are fulfilled for
a catalogue entry to get checked to show that it is included (through
<Module>xxxx</Module> entries in your catalogue entry). In our case we
were seeing that PB failed to determine that the module was included
and we got an X mark in front of our catalogue entry. We found out
this was caused by including the entries for the modules through a
#include file in our project .bib file. If we included the contents of
that include file in our .bib PB would happily check our catalogue
entry.

So, the following does not work:

; file: project.bib
#define PROJ_FILES_DIR $(_PUBLICROOT)\PROJ\OAK\FILES
moduleA.dll $(_flatreleasedir)\moduleA.dll NK
#include "$(PROJ_FILES_DIR)someotherstuff.bib"
----
; file: someotherstuff.bib
moduleB.dll $(_flatreleasedir)\moduleB.dll NK

And the following works

; file: project.bib
moduleA.dll $(_flatreleasedir)\moduleA.dll NK
moduleB.dll $(_flatreleasedir)\moduleB.dll NK

It is not really a major problem or anything but I would have expected
that PB would know how to deal with including files into your .bib
file (with respect to the catalog viewer). In our case there's lots to
include and separating them just makes sense.

Maybe MS can fix this or at least make users aware of ?

-- Ronald

Michel
Wed Apr 16 23:34:30 PDT 2008

So, where/how did you develop this expectation? Nowhere in the
documentation does MS say of hint that including other files is
supported in a bib file... It's like saying "I expected my car to be
able to fly over the traffic jams and I was really surprised that I was
unable to take-off... Maybe Chrysler can fix that or at least tell
people their cars don't fly..."


Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE Ltd.
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Ronald Sloot wrote:
> PB scans .bib files to determine if the requirements are fulfilled for
> a catalogue entry to get checked to show that it is included (through
> <Module>xxxx</Module> entries in your catalogue entry). In our case we
> were seeing that PB failed to determine that the module was included
> and we got an X mark in front of our catalogue entry. We found out
> this was caused by including the entries for the modules through a
> #include file in our project .bib file. If we included the contents of
> that include file in our .bib PB would happily check our catalogue
> entry.
>
> So, the following does not work:
>
> ; file: project.bib
> #define PROJ_FILES_DIR $(_PUBLICROOT)\PROJ\OAK\FILES
> moduleA.dll $(_flatreleasedir)\moduleA.dll NK
> #include "$(PROJ_FILES_DIR)someotherstuff.bib"
> ----
> ; file: someotherstuff.bib
> moduleB.dll $(_flatreleasedir)\moduleB.dll NK
>
> And the following works
>
> ; file: project.bib
> moduleA.dll $(_flatreleasedir)\moduleA.dll NK
> moduleB.dll $(_flatreleasedir)\moduleB.dll NK
>
> It is not really a major problem or anything but I would have expected
> that PB would know how to deal with including files into your .bib
> file (with respect to the catalog viewer). In our case there's lots to
> include and separating them just makes sense.
>
> Maybe MS can fix this or at least make users aware of ?
>
> -- Ronald

Paul
Thu Apr 17 08:45:50 PDT 2008

In this case, the cars do fly. You can use an include in a bib file.
Something like this:

#include "$(_TARGETPLATROOT)\drivers\<driverdir>\<yourbib>.bib"

I do this a lot in my platform.bib file to include the individual bib files
for various drivers. I've never tried #define in the bib file, however, and
don't know if it flies that way or not.

However, I don't know what the OP means by "(with respect to the catalog
viewer)". The catalog viewer doesn't really know anything about BIB files;
it's for viewing, surprise, the catalog.

Paul T.

"Michel Verhagen (eMVP)" <michel@nospam.box> wrote in message
news:efEdYUFoIHA.2632@TK2MSFTNGP04.phx.gbl...
> So, where/how did you develop this expectation? Nowhere in the
> documentation does MS say of hint that including other files is supported
> in a bib file... It's like saying "I expected my car to be able to fly
> over the traffic jams and I was really surprised that I was unable to
> take-off... Maybe Chrysler can fix that or at least tell people their cars
> don't fly..."
>
>
> Good luck,
>
> Michel Verhagen, eMVP
> Check out my blog: http://GuruCE.com/blog
>
> GuruCE Ltd.
> Microsoft Embedded Partner
> http://GuruCE.com
> Consultancy, training and development services.
>
> Ronald Sloot wrote:
>> PB scans .bib files to determine if the requirements are fulfilled for
>> a catalogue entry to get checked to show that it is included (through
>> <Module>xxxx</Module> entries in your catalogue entry). In our case we
>> were seeing that PB failed to determine that the module was included
>> and we got an X mark in front of our catalogue entry. We found out
>> this was caused by including the entries for the modules through a
>> #include file in our project .bib file. If we included the contents of
>> that include file in our .bib PB would happily check our catalogue
>> entry.
>>
>> So, the following does not work:
>>
>> ; file: project.bib
>> #define PROJ_FILES_DIR $(_PUBLICROOT)\PROJ\OAK\FILES
>> moduleA.dll $(_flatreleasedir)\moduleA.dll NK
>> #include "$(PROJ_FILES_DIR)someotherstuff.bib"
>> ----
>> ; file: someotherstuff.bib
>> moduleB.dll $(_flatreleasedir)\moduleB.dll NK
>>
>> And the following works
>>
>> ; file: project.bib
>> moduleA.dll $(_flatreleasedir)\moduleA.dll NK
>> moduleB.dll $(_flatreleasedir)\moduleB.dll NK
>>
>> It is not really a major problem or anything but I would have expected
>> that PB would know how to deal with including files into your .bib
>> file (with respect to the catalog viewer). In our case there's lots to
>> include and separating them just makes sense.
>>
>> Maybe MS can fix this or at least make users aware of ?
>>
>> -- Ronald

Steve
Thu Apr 17 10:49:56 PDT 2008

> However, I don't know what the OP means by "(with respect to the catalog
> viewer)". The catalog viewer doesn't really know anything about BIB
> files; it's for viewing, surprise, the catalog.

Actually that's not quite true. The "viewer" uses the driver resolver to
display which drivers will end up in the image. The Driver resolver knows
all about BIB files so syntax the resolver can't handle will cause issues
for the catalog view.


--
Steve Maillet
Program Manager - .NET Micro Framework

Paul
Thu Apr 17 10:58:31 PDT 2008

Doesn't seem to give any problems with my BIB files that have includes in
them. Of course, they're just in my platform stuff, and I'm not trying to
use #define. Kind of makes me wonder if the included file has a syntax
error in it.

Paul T.

"Steve Maillet [MSFT]" <smaillet_at_microsoft_com@nospam.com> wrote in
message news:OiHO0NLoIHA.2188@TK2MSFTNGP04.phx.gbl...
>> However, I don't know what the OP means by "(with respect to the catalog
>> viewer)". The catalog viewer doesn't really know anything about BIB
>> files; it's for viewing, surprise, the catalog.
>
> Actually that's not quite true. The "viewer" uses the driver resolver to
> display which drivers will end up in the image. The Driver resolver knows
> all about BIB files so syntax the resolver can't handle will cause issues
> for the catalog view.
>
>
> --
> Steve Maillet
> Program Manager - .NET Micro Framework
>
>

Michel
Thu Apr 17 11:45:36 PDT 2008

Oh man... I need to look into the car market some more... :|


Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE Ltd.
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Paul G. Tobey [eMVP] wrote:
> In this case, the cars do fly. You can use an include in a bib file.
> Something like this:
>
> #include "$(_TARGETPLATROOT)\drivers\<driverdir>\<yourbib>.bib"
>
> I do this a lot in my platform.bib file to include the individual bib files
> for various drivers. I've never tried #define in the bib file, however, and
> don't know if it flies that way or not.
>
> However, I don't know what the OP means by "(with respect to the catalog
> viewer)". The catalog viewer doesn't really know anything about BIB files;
> it's for viewing, surprise, the catalog.
>
> Paul T.
>
> "Michel Verhagen (eMVP)" <michel@nospam.box> wrote in message
> news:efEdYUFoIHA.2632@TK2MSFTNGP04.phx.gbl...
>> So, where/how did you develop this expectation? Nowhere in the
>> documentation does MS say of hint that including other files is supported
>> in a bib file... It's like saying "I expected my car to be able to fly
>> over the traffic jams and I was really surprised that I was unable to
>> take-off... Maybe Chrysler can fix that or at least tell people their cars
>> don't fly..."
>>
>>
>> Good luck,
>>
>> Michel Verhagen, eMVP
>> Check out my blog: http://GuruCE.com/blog
>>
>> GuruCE Ltd.
>> Microsoft Embedded Partner
>> http://GuruCE.com
>> Consultancy, training and development services.
>>
>> Ronald Sloot wrote:
>>> PB scans .bib files to determine if the requirements are fulfilled for
>>> a catalogue entry to get checked to show that it is included (through
>>> <Module>xxxx</Module> entries in your catalogue entry). In our case we
>>> were seeing that PB failed to determine that the module was included
>>> and we got an X mark in front of our catalogue entry. We found out
>>> this was caused by including the entries for the modules through a
>>> #include file in our project .bib file. If we included the contents of
>>> that include file in our .bib PB would happily check our catalogue
>>> entry.
>>>
>>> So, the following does not work:
>>>
>>> ; file: project.bib
>>> #define PROJ_FILES_DIR $(_PUBLICROOT)\PROJ\OAK\FILES
>>> moduleA.dll $(_flatreleasedir)\moduleA.dll NK
>>> #include "$(PROJ_FILES_DIR)someotherstuff.bib"
>>> ----
>>> ; file: someotherstuff.bib
>>> moduleB.dll $(_flatreleasedir)\moduleB.dll NK
>>>
>>> And the following works
>>>
>>> ; file: project.bib
>>> moduleA.dll $(_flatreleasedir)\moduleA.dll NK
>>> moduleB.dll $(_flatreleasedir)\moduleB.dll NK
>>>
>>> It is not really a major problem or anything but I would have expected
>>> that PB would know how to deal with including files into your .bib
>>> file (with respect to the catalog viewer). In our case there's lots to
>>> include and separating them just makes sense.
>>>
>>> Maybe MS can fix this or at least make users aware of ?
>>>
>>> -- Ronald
>
>

Ronald
Fri Apr 18 04:42:32 PDT 2008

For what it's worth, there is no syntax error otherwise I wouldn't be
able to build images using it.

This is only causing a problem with the catalog viewer.

I am simply asking if someone at MS who happens to stare at that code
some day to take a look and check if the parser used will also check
the include files that are used in the .bib file. As far as I have
seen from using a file monitor, it does not.

-- Ronald