User forums > Using Code::Blocks

update.bat problem?

<< < (2/2)

ollydbg:

--- Quote from: jens on November 05, 2009, 06:36:03 pm ---
--- Quote from: ollydbg on November 05, 2009, 05:04:43 pm ---it seems the zip command will always run?

--- End quote ---

Yes, but notice the u-parameter, it means update, only newer (or not existant) files are added/replaced to in zip-file.

--- End quote ---

Sorry for the late reply. And thanks for the explanation, Jens and stahta01. :D

ollydbg:
Hi, all, it seems there are still something wrong in the update.bat.

About two days ago, I built the SVN code, and run update.bat. After that, I haven't built the C::B again.

Today, I check the file in F:\cb_svn\src\output, all the exe file and dll files show the "data modified" information as two days ago.

As expected, update.bat should run and exit doing nothing, because no files were updated.

But the actually thing is: I run the update.bat, it still take a while to finish, and all the files in F:\cb_svn\src\output were updated, now these files show "data modified" as today.

Jenna:
That's due to the strip command, it touches all executables and libraries and tries to strip sy,bols.
The zip-files (e.g.) should be untouched, at least they are here (WinXP SP3).

ollydbg:

--- Quote from: jens on November 16, 2009, 08:30:20 am ---That's due to the strip command, it touches all executables and libraries and tries to strip sy,bols.
The zip-files (e.g.) should be untouched, at least they are here (WinXP SP3).

--- End quote ---
Yes, that's true.
But:
Is there a mechanism that letting the strip command only apply on the updated DLL or EXE files?

Jenna:

--- Quote from: ollydbg on November 16, 2009, 08:37:19 am ---
--- Quote from: jens on November 16, 2009, 08:30:20 am ---That's due to the strip command, it touches all executables and libraries and tries to strip sy,bols.
The zip-files (e.g.) should be untouched, at least they are here (WinXP SP3).

--- End quote ---
Yes, that's true.
But:
Is there a mechanism that letting the strip command only apply on the updated DLL or EXE files?

--- End quote ---

I don't think, that there is a mechanism to tell strip reliable, that a file does not contain symbols.
That means it has to touch it always, and always scan for symbols, but it does not need to write it back to hdd if it does nothing, but that's a strip-thing and I don't know a parameter to avoid it.

Navigation

[0] Message Index

[*] Previous page