Re: Makeimg not copying project files to FLATRELEASEDIR
- From: "Dean Ramsier" <ramsiernospam@xxxxxxxxxx>
- Date: Thu, 9 Mar 2006 09:09:17 -0500
One thing to clear up (you probably already know), makeimg is not
responsible for doing the copy. That job belongs to buildrel. You need to
either run that step manually, or check the menu item so it happens
automatically. Make sure that process is happening instead of relying on
the batch file, see if it gets you anywhere.
--
Dean Ramsier - eMVP
BSQUARE Corporation
"Remi de Gravelaine" <gravelaine at aton dash sys dot fr> wrote in message
news:eFi9nd1QGHA.4300@xxxxxxxxxxxxxxxxxxxxxxx
Hi All,
I am working with PB 5.0 on an XP Pro - SP2 machine.
I recently lost the ability to make a change in Project.reg, launch
Makeimg (Make Run-Time Image) and see my change in the freshly generated
reginit.ini.
As a temporary workaround, I added a Custom Build Action to my Project
Settings in order to enforce the copy of the Project files in the Pre-Make
Image step:
copy %_PROJECTOAKROOT%\files\project.* %_FLATRELEASEDIR%
Looking at the output, I discovered that there was a file access issue:
makeimg: run command: cmd /C
C:\WINCE500\public\common\oak\misc\pbpremakeimg
Generating PBWorkspace Custom makeimg build step batch Files to
C:\WINCE500\PBWorkspaces\EBB615EX\WINCE500\EBB615_x86\oak
Done Generating PBWorkspace Custom makeimg build step batch Files
Doing PreMakeImage Custom Build Actions
C:\WINCE500\PBWorkspaces\EBB615EX\WINCE500\EBB615_x86\oak\files\project.bib
Le processus ne peut pas acc,der au fichier car ce fichier est utilis, par
un autre processus.
C:\WINCE500\PBWorkspaces\EBB615EX\WINCE500\EBB615_x86\oak\files\project.dat
Le processus ne peut pas acc,der au fichier car ce fichier est utilis, par
un autre processus.
C:\WINCE500\PBWorkspaces\EBB615EX\WINCE500\EBB615_x86\oak\files\project.db
Le processus ne peut pas acc,der au fichier car ce fichier est utilis, par
un autre processus.
C:\WINCE500\PBWorkspaces\EBB615EX\WINCE500\EBB615_x86\oak\files\project.reg
0 fichier(s) copi,(s).
Le processus ne peut pas acc,der au fichier car ce fichier est utilis, par
un autre processus.
Done Doing PreMakeImage Custom Build Actions
In english, the offending message states that "The process can't access
the file because this file is used by another process". Of course, I am
unable to see what other process could be accessing my Project files.
If I then "touch" the files with Platform Builder (i.e. forcing PB to
write them to the disk), the copy works, until the next boot...
Any hints and sugestions are welcome.
Remi
.
- Follow-Ups:
- Re: Makeimg not copying project files to FLATRELEASEDIR
- From: Remi de Gravelaine
- Re: Makeimg not copying project files to FLATRELEASEDIR
- References:
- Makeimg not copying project files to FLATRELEASEDIR
- From: Remi de Gravelaine
- Makeimg not copying project files to FLATRELEASEDIR
- Prev by Date: Re: Alternatives to TFAT?
- Next by Date: Win CE memory pages
- Previous by thread: Makeimg not copying project files to FLATRELEASEDIR
- Next by thread: Re: Makeimg not copying project files to FLATRELEASEDIR
- Index(es):
Relevant Pages
|