This particular problem has only happened on windows. Without first duplicating the problem, trying to fix it will be a shot in the dark. To dupliicate it may require about 8 cpu cores and ming-make on windows. Going after this on linux misunderstands this problem I think.
I am glad Brian started a new thread for it, it is very specific. On Jan 24, 2013 3:23 AM, "Martijn Kuipers (Private)" < [email protected]> wrote: > Hi, > > I had a similar problem some years ago with CMake. > The solutions then was to add "add_dependencies" to the targets. From > cmake.org > <quote> > add_dependencies: Add a dependency between top-level targets. > > add_dependencies(target-name depend-target1 > depend-target2 ...) > > Make a top-level target depend on other top-level targets. A top-level > target is one created by ADD_EXECUTABLE, ADD_LIBRARY, or ADD_CUSTOM_TARGET. > Adding dependencies with this command can be used to make sure one target > is built before another target. See the DEPENDS option of ADD_CUSTOM_TARGET > and ADD_CUSTOM_COMMAND for adding file-level dependencies in custom rules. > See the OBJECT_DEPENDS option in SET_SOURCE_FILES_PROPERTIES to add > file-level dependencies to object files. > </quote> > > I don't have a kicad build environment ready. If nobody gets to it first I > can see if I can make some time. (It would be on Linux though, as my MBP is > too slow). > > /Martijn > > On Jan 24, 2013, at 8:32 AM, Brian Sidebotham <[email protected]> > wrote: > > Thanks for your feedback Dick. I'll try and have a look into it to see > what's going on. > > Best Regards, Brian. > > > On 23 January 2013 19:54, Dick Hollenbeck <[email protected]> wrote: > >> On 01/23/2013 12:43 PM, Brian Sidebotham wrote: >> > I used to think these problems were solely down to mingw32-make, >> however from the other >> > cmake problem, perhaps some of them are not. >> > >> > I've not seen this problem before, this is the first time I've come >> across it, but it is >> > repeatable. >> >> >> It is repeatable until you change something. This is a race condition I >> think, so don't >> be fooled into thinking it is a new bug, or that if it goes away it has >> been necessarily >> fixed. >> >> So in other words, it is repeatable only for the moment. >> >> And while it is you may want to try and nail it. >> >> >> If you want instead to sweep it under the rug, and simply hope it does >> not reappear, you >> could run with >> >> -j3 >> >> >> That might get you by, until somebody has time to look at it in greater >> detail. >> >> Some things I would suggest: >> >> compare the output of cmake (i.e. makefiles) on between linux and windows. >> >> especially wrt to this make target. >> >> Base on those results: >> >> Try a newer mingw32-make. Try a newer cmake. >> >> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > > >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
