Actually, fist do resync, "deliver -delete", update sources, replicate
changes in headers, if needed- move headers+correct "#includes", build
sources. You will see quite quickly if you did something wrong, what to
to will be obvious...
Vladimir
Was the only thing the move of some headers? Delivered headers only?
Moving of delivered headers from f.e. svx/inc into svx/inv/svx. Adapting
includes accordingly. Adapting d.lst files.
Do we have to do any changes in CWS chart2mst3, where we added a new
module with new headers?
-Bjoern
I more detail:
If you did not touch headers, no action is required.
If you changed existing headers or introduced new ones, check in
prj/d.lst, whether those headers are subject to 'headbu' action. If they
are not: no action required.
If your header was 'hedabu'ed it most probably got removed by Vladimir
and moved to an new location, as stated above. Moving files is not
really supported by cvs. Therefore you have to check your changes, i.e.
cvs diff -r <CWS_ANCHOR> -r <cws_branch> <file> and apply those changes
to the moved header. If you introduced a new one subject to hedabu, move
it to the appropriate directory and adapt include directives (i.e. for
the above svx example change #include "myheader.hxx" into #include
"svx/myheader.h" where needed). Finally, adapt d.lst.
<svx/myheader.h>
Rüdiger
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
