Eclipse Community Forums: DSDP - Real-Time Software Components (RTSC)

Help

Home

Home » Archived » DSDP - Real-Time Software Components (RTSC) » Change "Warning" to "Remark"

Show: Today's Messages :: Show Polls :: Message Navigator

Change "Warning" to "Remark" [message #3247]

Tue, 19 May 2009 18:22

Chris Ring

Messages: 16
Registered: July 2009
Location: Santa Barbara, CA

Junior Member

I'd like to suggest that the current "Warning: no config.bld file was
found along the package path..." emitted whenever the
$XDC_INSTALL_DIR/packages/config.bld is used be changed to a "Remark". Or
perhaps provide some way to say "I know I'm using that config.bld, please
don't warn me about it".

Some of my packages don't contain any binaries, and the default config.bld
provided in XDCtools is exactly what I want. But my build logs show this
as a warning - and I prefer to build without warnings.

Open to other workarounds... I fundamentally just want to avoid the
Warning msg.

Chris

Report message to a moderator

Re: Change "Warning" to "Remark" [message #3349 is a reply to message #3247]

Wed, 20 May 2009 14:47

Dave Russo

Messages: 172
Registered: July 2009

Senior Member

Chris Ring wrote:
> I'd like to suggest that the current "Warning: no config.bld file was
> found along the package path..." emitted whenever the
> $XDC_INSTALL_DIR/packages/config.bld is used be changed to a "Remark".
> Or perhaps provide some way to say "I know I'm using that config.bld,
> please don't warn me about it".
>
> Some of my packages don't contain any binaries, and the default
> config.bld provided in XDCtools is exactly what I want. But my build
> logs show this as a warning - and I prefer to build without warnings.
>
We added the warning because too many users complained that the when
their config.bld was not picked up by the tools (e.g., it was not on the
package path), the xdc command would complete without any indication of
a problem.

> Open to other workarounds... I fundamentally just want to avoid the
> Warning msg.
>
The "last resort" config.bld is $XDCROOT/etc/config.bld and is only used
when no config.bld can be found in the current working directory or
along the package path.

You can explicitly specify the config.bld to use on the command line,
place a config.bld in the package's base, or place it in any directory
named on the package path.

You could create a repository that just contains your config.bld and
place this on your package path. Note, however, the latest release of
the path tool will warn about repositories that do not contain packages
(doh!)

> Chris
>

Report message to a moderator

Re: Change "Warning" to "Remark" [message #3382 is a reply to message #3349]

Wed, 20 May 2009 16:17

Chris Ring

Messages: 16
Registered: July 2009
Location: Santa Barbara, CA

Junior Member

dave russo wrote:
> Chris Ring wrote:
>> I'd like to suggest that the current "Warning: no config.bld file was
>> found along the package path..." emitted whenever the
>> $XDC_INSTALL_DIR/packages/config.bld is used be changed to a
>> "Remark". Or perhaps provide some way to say "I know I'm using that
>> config.bld, please don't warn me about it".
>>
>> Some of my packages don't contain any binaries, and the default
>> config.bld provided in XDCtools is exactly what I want. But my build
>> logs show this as a warning - and I prefer to build without warnings.
>>
> We added the warning because too many users complained that the when
> their config.bld was not picked up by the tools (e.g., it was not on the
> package path), the xdc command would complete without any indication of
> a problem.

Got it, and I like it - my only issue is that it's classified as a
"Warning", so it makes my builds chatty and full of "Warnings".

>> Open to other workarounds... I fundamentally just want to avoid the
>> Warning msg.
>>
> The "last resort" config.bld is $XDCROOT/etc/config.bld and is only used
> when no config.bld can be found in the current working directory or
> along the package path.
>
> You can explicitly specify the config.bld to use on the command line,
> place a config.bld in the package's base, or place it in any directory
> named on the package path.

If I explicitly say XDCBUILDCFG=$XDCROOT/etc/config.bld on the cmd line,
it'd be nice if the Warning goes away? (Can $XDCROOT/etc/config.bld
detect that and only conditionally issue the warning?)

Or is the only option to provide my own one-line config.bld?

> You could create a repository that just contains your config.bld and
> place this on your package path. Note, however, the latest release of
> the path tool will warn about repositories that do not contain packages
> (doh!)
>
>> Chris

Report message to a moderator

Re: Change "Warning" to "Remark" [message #3414 is a reply to message #3382]

Wed, 20 May 2009 19:09

Dave Russo

Messages: 172
Registered: July 2009

Senior Member

Chris Ring wrote:
>> You can explicitly specify the config.bld to use on the command line,
>> place a config.bld in the package's base, or place it in any directory
>> named on the package path.
>
> If I explicitly say XDCBUILDCFG=$XDCROOT/etc/config.bld on the cmd line,
> it'd be nice if the Warning goes away? (Can $XDCROOT/etc/config.bld
> detect that and only conditionally issue the warning?)
>
It's possible but not cheap: the config.bld can check the environment
for XDCBUILDCFG and compare it to java.io.File('.") + "/config.bld".

> Or is the only option to provide my own one-line config.bld?
>
With the current release, yes. Is it likely that this file will remain
just a one-liner? I often add "Pkg.attrs.archiver = 'zip';", for example.

>> You could create a repository that just contains your config.bld and
>> place this on your package path. Note, however, the latest release of
>> the path tool will warn about repositories that do not contain
>> packages (doh!)
>>
>>> Chris

Report message to a moderator

Previous Topic:	To Rebuild the Package ... or not
Next Topic:	Using target properties in a makefile rule

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Oct 12 06:42:52 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter