On 24 Oct 2014, at 3:25 , Henrik Johansen <henrik.s.johansen@veloxit.no> wrote:
On 24 Oct 2014, at 3:20 , Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 24 Oct 2014, at 15:10, Marcus Denker <marcus.denker@inria.fr> wrote:
Isn't that for what NativeBoost prepareForProduction is used?
Yes! Now I remember, we solved that usecase already.
Good.
Nice!
Maybe it should run after each build, or is that platform dependent ?
Nonononono. The NB trailer only knows how to reinstall source from an original trailer with source pointer, so after first invocation, it will lose the source and start failing at next image startup.
Cheers, Henry
Disregard that, prepareForProduction is implemented differently from what I described, and the argument mapping no longer works they way I seemed to remembered, using the cache if present. It should be safe to called when building, and allows dropping the changes file later on with no bad side-effects like my little hack. Cheers, Henry