This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I updated from NB69 to NB73B2 on all my development workstations regardless the platform (I had to use NB73 as NB72 contains some bug - see http://netbeans.org/bugzilla/show_bug.cgi?id=222195). Now all my C/C++ projects open/compile well on three platforms - PowerPC, Linux and OSX. The only remaining and really anoying problem is this: 1. I open the projects on the Linux workstation. 2. All the C/C++ projects (after parsing) appear modified. 3. I commit the modifications onto SVN repository. 4. I update from the SVN repository on the MacBook Pro workstation. 5. I open all the projects on that Mac. 6. After parsing, all the projects become modified again. 7. So I commit onto the SVN repository and move back to Linux. 8. And history repeats... The modified files when switching between development platforms are makefiles. It is important to have fixed as the development team cooperating on the project works partialy on Macs and partially on Linuxes.
Please provide additional info: What files are changed? What are diff of changed files?
Created attachment 129470 [details] Beginning of the list of modified files
Created attachment 129471 [details] The diff of the first modified file on the list
You should exclude from commit following files: - nbproject/private/* - nbproject/*.mk - nbproject/*.bash *** This bug has been marked as a duplicate of bug 192036 ***
The private project subdirs are already ignored by SVN. The other files are NOT in the private subfolder. Are you sure that I will not break anything by that? (Sorry, I am asking for double confirmation as it sounds like a NB design inconsistency which I was not experiencing in NB69) So all these files are now generated from scratch during every NB start? (Sorry, I am asking as I always try to understand at least a bit more than I have to)
(In reply to comment #5) > The private project subdirs are already ignored by SVN. > > The other files are NOT in the private subfolder. > Are you sure that I will not break anything by that? > (Sorry, I am asking for double confirmation as it sounds like a NB design > inconsistency which I was not experiencing in NB69) > > So all these files are now generated from scratch during every NB start? > (Sorry, I am asking as I always try to understand at least a bit more than I > have to) Primary meta info is in the files: - nbproject/project.xml - nbproject/configurations.xml Other files are secondary and (re)generated when project properties are changed or clean/build is performed.
I have one more file which was not mentioned yet: - project.properties Delete from or keep on the SVN? IMHO: Then those secondary files should have been located in the private directory (but its minor once one knows...). OK, I will risk deleting...
(In reply to comment #7) > I have one more file which was not mentioned yet: > - project.properties It should be empty. So it can be versioned.
Well, I did it and now I am having shis on clean/build: Makefile:96: nbproject/Makefile-impl.mk: No such file or directory make[2]: *** No rule to make target `nbproject/Makefile-impl.mk'. Stop. make[1]: *** [.clean-subprojects] Error 2 make: *** [.clean-impl] Error 2
(In reply to comment #9) > Well, I did it and now I am having shis on clean/build: > > Makefile:96: nbproject/Makefile-impl.mk: No such file or directory > make[2]: *** No rule to make target `nbproject/Makefile-impl.mk'. Stop. > make[1]: *** [.clean-subprojects] Error 2 > make: *** [.clean-impl] Error 2 Sorry, this file (nbproject/Makefile-impl.mk) should be versioned.
(In reply to comment #10) > (In reply to comment #9) > > Well, I did it and now I am having shis on clean/build: > > > > Makefile:96: nbproject/Makefile-impl.mk: No such file or directory > > make[2]: *** No rule to make target `nbproject/Makefile-impl.mk'. Stop. > > make[1]: *** [.clean-subprojects] Error 2 > > make: *** [.clean-impl] Error 2 > Sorry, this file (nbproject/Makefile-impl.mk) should be versioned. For details see article: http://www.oracle.com/technetwork/articles/servers-storage-dev/ide-version-control-1719427.html
OK, that seems to be my fault. Now it works. The impl files were also recreated. And it seems to build fine for all targets on both platforms. So where is the truth? Shall the impl.mk files be versioned or not?
(In reply to comment #12) > OK, that seems to be my fault. Now it works. > > The impl files were also recreated. And it seems to build fine for all targets > on both platforms. > > So where is the truth? Shall the impl.mk files be versioned or not? Is link to article clickable? I think the article can answer to all your questions.
Yes, I am just reading it. Please note that you made me a bit wrong and I need to fix the projects as fast as possible. The article is very long and your answer (if you know) could only be just YES/NO - which would have been helpful...
(In reply to comment #14) > Yes, I am just reading it. > > Please note that you made me a bit wrong and I need to fix the projects as fast > as possible. > > The article is very long and your answer (if you know) could only be just > YES/NO - which would have been helpful... DO not put nbproject/Makefile-impl.mk under VCS. The file is regenerated when you change project properties in the IDE or clean/build in the IDE.
OK, in the mean time I did my best to check all the targets and platforms. Everything seems to be fine. Thank you for all your assistance. Also thank you for pointing me to that article, I am going through it only when my test builds are in progress, but it seems usefull and I will finish reading it. And finally thank you for confirming that deleting the nbproject/Makefile-impl.mk files was not that wrong.
Really very useful article. Pointed me to one more potential problem with my a bit complex suite of projects (some of them are managed, some unmanaged, two different development platforms, three different toolchains, three different configurations, some crosscompiled). Thank you again...
(In reply to comment #17) > Really very useful article. > > Pointed me to one more potential problem with my a bit complex suite of > projects (some of them are managed, some unmanaged, two different development > platforms, three different toolchains, three different configurations, some > crosscompiled). > > Thank you again... NB 7.3 supports unmanaged projects better then previous NB. Thanks for example of diff. You show unknown blinking in the managed project (unpredictable order of targets in the generated make file). I'll fix it in bug #192036.
Well I have to make an off-topic complaint on (otherwise great) NetBeans... I am using both NetBenas and Eclipse. I originally selected NetBeans as it has much cleaner UI and it offered all I needed. I had to switch to Eclipse as Oracle dropped dupport for Python in Netbeans. Which makes my projects less integrated - originally it was in a single IDE - extremely nicely integrated together, not it is in two different IDEs :((( From that point of view, my original decision was bad as NetBeans is now controlled by Oracle who is able to drop projects like OpenOffice or Python in NetBeans without any excuse, while Eclipse seems to continue consistently as the users expect it... Anyway, I know it is not your fault :;) Merry Chritmas!
(In reply to comment #19) > I had to switch to Eclipse as Oracle dropped dupport for Python in Netbeans. > Anyway, I know it is not your fault :;) Btw, just yesterday I wanted Python and installed it in 7.3 by adding update center: http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/lastStableBuild/artifact/nbbuild/nbms/updates.xml.gz So, It works in 7.3 :-) Merry Christmas!
Of course, I am watching the netbeans wiki related to NetBeans. But last time when I did this attempt (that was with NB71), the NetBeans completely stopped working (hanging in the splash-screen or something like that). There stil must be some unresolved bug report related to this problem. Nothing helped me out of that stuck - I just deleted NB71 and stayed with NB69... Frenkly speaking, since that incident, I considered Python for NetBeans dead - also the development is stoped, the deadlock project disabled with last change in yr. 2010. So you think I may give it one more chance?