User forums > Nightly builds

The 02 November 2012 build (8500) is out.

<< < (6/8) > >>

ollydbg:

--- Quote from: ollydbg on November 03, 2012, 02:56:31 pm ---The bad thing is: if I rebuild C::B, I will sometimes see the warning message(see below)

Does this mean that my "PATH" was locked by some one/software?

--- End quote ---

I found a workaround, for those who have the same issue, you can give C::B a new and clean environment, like, start C::B in the console with the command:

--- Code: ---@set PATH=E:\code\common_bin;C:\Program Files\SlikSvn\bin
start codeblocks.exe

--- End code ---

Here, the PATH variable is set manually, and my c::b build and works fine.

I guess that my PATH have too many strings, which cause the SetEnvironmentVariable function fail. :)

White-Tiger:
well this isn't about this specific nightly... but rather revision 8536, it simply breaks the windows build^^
It's not possible to define "unused" as this is often a variable name used with windows. eg. in "winnt.h" it is used for the "DECLARE_HANDLE" define. (MinGW64)

oBFusCATed:
White-Tiger: http://forums.codeblocks.org/index.php/topic,17067.msg116546/topicseen.html#msg116546

gd_on:
Something new in svn 8549 (or a bug ?), but, under Windows 7, an AppData has been created in my Program files (x86)\codeblocks folder and my previous default.conf is not found. Apparently, it's in this new folder that C::B parameters are stored. Is it normal ?
After reverting to svn 8543, everything is OK again. Is it a bug ? a new behaviour ? But, in that last case, if Program files is write protected, a standard behaviour in Windows 7, I'm not sure it's a good idea : within the user's profile it's better.

gd_on

Edit : I have made a full rebuild and an install in a clean empty folder, and everything is OK with svn 8549. Strange. Sorry for the noise !

AndyJ:
Thanks for all the great work recently!

I noticed a few nightlies back that on my 2 monitor Win-XP system CodeBlocks no longer remembers that it was last run maximised on my 2nd monitor (this used to work). It did however remember that it was on the the 2nd monitor if not maximised. With the latest nightly, it now always seems to start on my primary monitor regardless of where it was when it was last closed - any ideas?

Andy

Edit: Oops, this really applies to the Nov 11th nightly (which now seems to have become something different...)

Navigation

[0] Message Index

[#] Next page

[*] Previous page