Lots of "File not found"-Errors on building a configuration

[Peter Zahn]

Hello,

i am working on an XPe-configuration, which uses components from the
mainboard vendor (Kontron). Every component (hardware drivers) brings its own
Repository. As the components weren't released, i released them and imported
them a second time. This includes importing the component-files (i had to
delete the repository first, to do this without write permission errors). The
repositories were, as i see, successfully created.
Now i get about 70 of the following "File not found"-Messages on building
the configuration:

Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"igxpdv32.dll"
R: Error 1005: File not found: "igxpdv32.dll"

The part, that confuses me is, that in contrast to this message, the files
are included in the build.

Now i'd like to get rid of this message, and "repair" the database, so that
the files are no more recognized as missing. Maybe someone can tell me, what
is causing this error message, and how i could repair it.

Thanks in advance,

Peter Zahn

 

[DPM]

Hello,

i am working on an XPe-configuration, which uses components from the
mainboard vendor (Kontron). Every component (hardware drivers) brings its
own
Repository. As the components weren't released, i released them and
imported
them a second time. This includes importing the component-files (i had to
delete the repository first, to do this without write permission errors).
The
repositories were, as i see, successfully created.
Now i get about 70 of the following "File not found"-Messages on building
the configuration:

Error 1005 (0x3ED) in "PlatformLib::CopySrcFile2": File not found:
"igxpdv32.dll"
R: Error 1005: File not found: "igxpdv32.dll"

The part, that confuses me is, that in contrast to this message, the files
are included in the build.

Now i'd like to get rid of this message, and "repair" the database, so
that
the files are no more recognized as missing. Maybe someone can tell me,
what
is causing this error message, and how i could repair it.

Thanks in advance,

Peter Zahn

Peter,

When you create a component in Component Designer, one of its properties is
an associated repository. Each component must point to the appropriate
repository; if it does not, then you will get "File not found" errors in
Target Designer when it tries to pull the files out of the repository.

Each repository has a source path; when the component is imported the files
are copied from the source path into a repository. If that path is not
correct you will get "File not found" errors when you import the component
with Database Manager.

From what you said I suspect that the link between the component and its
repository was either not made, or made improperly.

From what I can see, "releasing" a component is merely a way of tracking a
component's status - it has nothing to do with files or their repositories.

Regards,
Dean

 

[Peter Zahn]

Hello Dean,

thanks for your reply!

From what you said I suspect that the link between the component and its
repository was either not made, or made improperly.

I double checked the path to the assigned repository for one component in
"Component Database Manager" (Repository tab -> Change location), which
seemed to be correct.

an associated repository. Each component must point to the appropriate
repository; if it does not, then you will get "File not found" errors in
Target Designer when it tries to pull the files out of the repository.

Now, what is unclear to me, how does a component reference a repository? As
i can see in "Component Database Manager", each repository consists of a name
and a version. Does TD simply look for a repository with the specific name
and version, or is there a kind of "database connection" between component
and repository? If yes, could it be that this "link" gets broken?

From what I can see, "releasing" a component is merely a way of tracking a
component's status - it has nothing to do with files or their repositories.

I wrote this, because it was the reason for the problem. As i understand,
after component changes (update or release), it is necessary to re-import it
the normal way. As i did this, the import failed becaus of write permission
errors, which i could solve by renaming the specific repository folder, so
that the import created an identical, new folder. Did i make a mistake in
this procedure?

And general about the update of components: As i see, there are two possible
ways: Changes in the component, but repository files are identical, or
changes in the component and changes in the repository files.
What is the right procedure in both cases. First, only re-import the
component without importing files? And in the second case, i should change
the repository version and re-import with files? Would this create a second,
parallel repository for this component? Or how in general i should handle the
update process?

I temporarily fixed the problem by adding all "Not Found"-Files to a
separate directory, which i added as "Additional Files Directory", which
worked, but of course this is a rather dirty solution as i think.

Peter Zahn

 

[DPM]

Hello Dean,

thanks for your reply!


I double checked the path to the assigned repository for one component in
"Component Database Manager" (Repository tab -> Change location), which
seemed to be correct.


Now, what is unclear to me, how does a component reference a repository?
As
i can see in "Component Database Manager", each repository consists of a
name
and a version. Does TD simply look for a repository with the specific name
and version, or is there a kind of "database connection" between component
and repository? If yes, could it be that this "link" gets broken?

Start CD and open your .sld. On the left pane under "Windows XP Embedded
Client (x86)" you'll see a Components folder - in it you should have at
least 1 component. Click a component, and on the right pane in the bottom
block you'll see a field named "Repository". If the field contents does not
have the name of the repository where the files enumerated in the Files list
(revealed by expanding your component) are kept then TD will throw "File not
found" errors. This in the magic link that tells TD in what repository to
look for the files you've added to your component.

I wrote this, because it was the reason for the problem. As i understand,
after component changes (update or release), it is necessary to re-import
it
the normal way. As i did this, the import failed becaus of write
permission
errors, which i could solve by renaming the specific repository folder, so
that the import created an identical, new folder. Did i make a mistake in
this procedure?

Probably because I'm lazy I've never bothered to release my custom
components. TD throws warnings when building unreleased components but
otherwise builds the image.

 

[Gokul]

Hi Peter,

From your post i assume you have created repository but not linked to the
component.
you have to link the component to the repository using component designer
tool.

 

[Peter Zahn]

Start CD and open your .sld. On the left pane under "Windows XP Embedded

Client (x86)" you'll see a Components folder - in it you should have at
least 1 component. Click a component, and on the right pane in the bottom
block you'll see a field named "Repository". If the field contents does not
have the name of the repository where the files enumerated in the Files list
(revealed by expanding your component) are kept then TD will throw "File not
found" errors. This in the magic link that tells TD in what repository to
look for the files you've added to your component.

OK, i'll double-check all my components for having this link correct. Thanks
for your detailled answer, now the repositories seem a bit more logical to me.

Peter Zahn

 

[spanimage]

OK, i'll double-check all my components for having this link correct. Thanks
for your detailled answer, now the repositories seem a bit more logical to me.

Peter Zahn

Hi
let me know if you need any help
we are in a same boat so that we can help each other building the
embedded edition.

Regards
SHAKEEELA AHMMED