Project does not rebuild

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Project does not rebuild

1,192件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by gbm on Tue Oct 01 06:05:03 MST 2013
I am using LPCXpresso since version 3.4. Some problems with dependency scan had appeared and disappeared in various versions. Things got significantly worse with 5.2.6 and 6.0.2 seems to be a disaster. When I make changes to .h file included directly in most of my .c source files, the project does not rebuild and make says it's up to date. Rebuilding the index doesn't help. The only way to get it rebuilt is to use Clean.  Am I missing something very obvious and stupid?
0 件の賞賛
返信
7 返答(返信)

1,129件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by yasla on Thu Oct 10 05:51:46 MST 2013
I have had the same issue - changes in header files do not trigger new re-build.
"Refresh Policy" check solved the problem for me too!
In my case it was not empty but points to quite different project ... suppose result of my "work" importing/exporting between projects trying to solve the issue.
0 件の賞賛
返信

1,129件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by gbm on Wed Oct 02 09:17:14 MST 2013
0. It's not that easy to post the project; it's a commercial stuff and it has over 40 source files and 3 build configurations.
1. No paths in #include directives
2. Refresh policy tab in my project properties was empty! After ADDing my project folder as the only item in the resource list, the Build seems to work!
(Should I put the project folder there, or build target name?)
3. Indexer settings were ok.

Looks like the target was mysteriously removed from Refresh Policy list during one of the last LPCxpresso updates.

I have applied the suggested workaround to my first build configuration of the project, then switched to the second. The Refresh policy tab in the 2nd config is empty but this time the configuration target rebuilds correctly after any change to .h file, although it didn't rebuild before. Now that's another mystery...

Thanks for your help.
0 件の賞賛
返信

1,129件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Wed Oct 02 03:23:44 MST 2013
As we have previously stated without seeing your project, it is impossible to tell what is going on.

My best guess given that your project has been under development for a very long period of time, something in the project settings has become corrupt. A few possible things to check/change might be:

[list]
  [*]Check whether you are specifying include paths within the source code itself. In particular look to see if in some place your are using Windows style relative pathnames, ie of the form "..\" and in others you are using Unix style, ie of the form "../". If this is the case try changing all such usage to Unix style ("../"). Making such a change should just take a couple of minutes using the IDE's search and replace.
[/list]

[list]
  [*]Go to Project Properties -> C/C++ Build (top level) -> Refresh Policy tab. The name you see displayed should match exactly with the name of your project. If this is not the case, use the delete option to remove it, then the "Add Resource" to select your project again.
[/list]

[list]
  [*]Check the indexer settings in Window -> Preferences -> C/C++ Indexer. In particular, ensure that “Index source and header files opened in editor” is selected.
[/list]
Note that these are only guesses, but it would be interesting to know whether any of these help at all.

To be honest though, given the age of your project and the problems you are seeing, it might actually be simpler to just recreate it again.

Regards,
LPCXpresso Support
0 件の賞賛
返信

1,129件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by cfbsoftware on Tue Oct 01 15:27:31 MST 2013
As a simple test in an attempt to reproduce your problem I first built Blinky and then made a change to LPC18xx.h (just typed in some garbage). It was picked up when I next tried an incremental build. I conclude from this that if indeed it doesn't work then it is only in *some* situations that it doesn't work.

Try a similar experiment yourself and if that works OK try to identify what is peculiar in your original situation.
0 件の賞賛
返信

1,129件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Oct 01 07:53:23 MST 2013
Without a PROJECT that I can use to reproduce on my machine, here, I am unable to help.
0 件の賞賛
返信

1,129件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by gbm on Tue Oct 01 07:17:53 MST 2013
The exact problem is:

I have mxxx.h file included in main.c and some other .c files. If I change some constant definitions in mxxx.h and use Build button, I can see the following message:

15:09:26 **** Incremental Build of configuration MSDupdate for project m2012 ****
make all
make: Nothing to be done for `all'.

15:09:27 Build Finished (took 1s.14ms)

Build worked mostly correctly in LPCXpresso 3.x, 4.x, 5.1.x and up to 5.2.4. In 5.2.6 the project frequently refused to build. In 6.0.2 the project never rebuilds after any changes made to mxxx.h. The only way to get it compiled is to use Project->Clean.
Essentially incremental build doesn't work, only manual full project compile works. Make dependency scan seems to ignore all changes made to .h files - the unchanged .c file including the changed .h file does not recompile when using Build (hammer button). Only changed .c files are compiled.
0 件の賞賛
返信

1,129件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Oct 01 06:40:14 MST 2013
Possibly, but without your project, or an example that shows the exact problem, it is very difficult to say.
0 件の賞賛
返信