*.appli change -> full rebuild?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

*.appli change -> full rebuild?

Jump to solution
2,629 Views
s_kalop
Contributor I

Hello, i have simple library project(CW10.2.1) about of 300 source files. Every time i make changes in *appli file of this project(data placement) full rebuild is needed(it's consumed a lot of time), but change i've made concerns just one file. Are there some methods to prevent full rebuilding when *appli is changed?

Labels (1)
0 Kudos
Reply
1 Solution
2,490 Views
CrasyCat
Specialist III

Hello

The .appli file you are using is used as input for all the source file within the project. So there is a direct dependency between each of the source file and the .appli file.

Any change inside of the .appli file implies a full rebuild of the application.

The IDE only noticed the .appli file has been changed since the last time the source file has been built.

So you cannot prevent CodeWarrior from rebuilding the whole application after a change in the .appli file.

Now depending what you are trying to do in the .appli file, you may want to use the corresponding pragmas or __attribute__ in the single source file, instead of using the .appli file. 

This way the rebuild will only build the source files, which have been changed.

Be careful all commands inside of the.appli file do not have a correspondent pragma or __attribute__ notation. So using this variant really depends on what you are trying to achieve in the .appli file.

CrasyCat

View solution in original post

0 Kudos
Reply
2 Replies
2,491 Views
CrasyCat
Specialist III

Hello

The .appli file you are using is used as input for all the source file within the project. So there is a direct dependency between each of the source file and the .appli file.

Any change inside of the .appli file implies a full rebuild of the application.

The IDE only noticed the .appli file has been changed since the last time the source file has been built.

So you cannot prevent CodeWarrior from rebuilding the whole application after a change in the .appli file.

Now depending what you are trying to do in the .appli file, you may want to use the corresponding pragmas or __attribute__ in the single source file, instead of using the .appli file. 

This way the rebuild will only build the source files, which have been changed.

Be careful all commands inside of the.appli file do not have a correspondent pragma or __attribute__ notation. So using this variant really depends on what you are trying to achieve in the .appli file.

CrasyCat

0 Kudos
Reply
2,489 Views
s_kalop
Contributor I

Thank you

0 Kudos
Reply