Code::Blocks Forums

Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: whoknows on September 23, 2012, 07:05:51 pm

Title: Who tell me where's the "application log"
Post by: whoknows on September 23, 2012, 07:05:51 pm

Most plugin were not loaded after I built code::blocks & plugins and ran update.exe followed http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows (http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows).

Then I search the topic found http://forums.codeblocks.org/index.php?action=printpage;topic=7610.0 (http://forums.codeblocks.org/index.php?action=printpage;topic=7610.0), but I built code::blocks and plugins with the same evirentment, why it said "This usually happens when a plugin is built for a different version of code::blocks sdk"?

Most important thing, I think, is where to check the application log?

Attachment is the warning snapshot, almost all plugins were not loaded.

Title: Re: Who tell me where's the "application log"
Post by: whoknows on September 23, 2012, 07:20:57 pm

I'm sorry, I didn't had the svn.exe in PATH before.
I didn't know it's so important while I think it should be an building time error if so.
While I added it to PATH and rebuilt code::blocks, and ran update.bat, then the plugins worked.

Title: Re: Who tell me where's the "application log"
Post by: oBFusCATed on September 23, 2012, 07:34:23 pm

You don't need svn.exe for a proper build.

Title: Re: Who tell me where's the "application log"
Post by: Jenna on September 23, 2012, 07:38:06 pm

Run C::B from a console windows (cmd.exe) with the -v parameter to get more debug messages.

Title: Re: Who tell me where's the "application log"
Post by: whoknows on September 23, 2012, 07:46:22 pm

Quote from: oBFusCATed on September 23, 2012, 07:34:23 pm

You don't need svn.exe for a proper build.

Thanks, while I had it in PATH and rebuilt code::blocks then the plugins worked.

Title: Re: Who tell me where's the "application log"
Post by: whoknows on September 23, 2012, 07:47:39 pm

Quote from: jens on September 23, 2012, 07:38:06 pm

Run C::B from a console windows (cmd.exe) with the -v parameter to get more debug messages.

Good, Thanks :)