Author Topic: problem running nightly build  (Read 4355 times)

carnykur

  • Guest
problem running nightly build
« on: October 12, 2006, 10:35:54 am »
well, i've got this problem: i install c::b and it runs alright. then i copy files from nightlybuild into c::b folder but after that c::b rises an exception that it cann not read default.workspace file, actualy it claims that it can not read an end tag and than application stops. A few times it ran on, but raised lots of another exceptions about missing starting points of procedures in various dll's. i reinstalled c::b several times, i tried to delete the workspace file, but nothing worked.

i keep reinstalling and trying anything i can thing of and i'll be thankfull for any advice. i'm running on win xp.
« Last Edit: October 12, 2006, 10:43:49 am by carnykur »

carnykur

  • Guest
Re: problem running nightly build
« Reply #1 on: October 12, 2006, 10:39:03 am »
... in june i did the same thing and it worked. yesterday i thought myself that it is time to upgrade c::b and i ran into this mess.

Offline artoj

  • Almost regular
  • **
  • Posts: 206
  • Location: Supporting my team
    • http://ajonsson.kapsi.fi/
Re: problem running nightly build
« Reply #2 on: October 12, 2006, 10:44:19 am »

cpprooky

  • Guest
Re: problem running nightly build
« Reply #3 on: October 12, 2006, 11:12:41 am »
I think it's recommanded not to install a Night Build in the same folder than a C::B release.
Just uninstall your C::B release and create a new directory for the last NB where you will unzip the content of the Night Build .7z (with the two dlls needed : They can be downloaded from the same page than the NB package)
Then, you will just need to install a compiler (let's say MinGW) in another new directory.

One more thing : if you've installed a NB and want to install a newer NB, personnally, I delete evreything in the directory.
It happened to me that it has solved somes bugs in a NB.

 :lol:


carnykur

  • Guest
Re: problem running nightly build
« Reply #4 on: October 12, 2006, 11:15:25 am »
thanks. i found out, what was problem. c::b stored its configuration files in two places. i deleted files reported  in first exeption message and after that i did not read messages properly :) my fault.