Author Topic: Release 12.11 has arrived  (Read 100636 times)

Offline Alpha

  • Developer
  • Lives here!
  • *****
  • Posts: 1513
Re: Release 12.11 has arrived
« Reply #60 on: January 04, 2013, 06:39:18 pm »
I tried to compile it with the source code of the 12.11 version but the plugin fail at load =/
Did you compile only the plugin, or the whole program?

MinGW (a quite recent version [...]
What version exactly?  Also, SJLJ or DW2?

Offline Taiki

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: Release 12.11 has arrived
« Reply #61 on: January 04, 2013, 06:58:19 pm »
I tried to compile it with the source code of the 12.11 version but the plugin fail at load =/
Did you compile only the plugin, or the whole program?
Only the plugin.

MinGW (a quite recent version [...]
What version exactly?  Also, SJLJ or DW2?
It seems to be GCC 4.7.2, and as I didn't saw any mention of those acronyms, I guess it's SJLJ
« Last Edit: January 04, 2013, 07:08:28 pm by Taiki »

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11939
    • Travis build status
Re: Release 12.11 has arrived
« Reply #62 on: January 04, 2013, 07:25:12 pm »
gcc --version executed in the command line will tell you the version.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Alpha

  • Developer
  • Lives here!
  • *****
  • Posts: 1513
Re: Release 12.11 has arrived
« Reply #63 on: January 04, 2013, 09:18:11 pm »
It seems to be GCC 4.7.2, and as I didn't saw any mention of those acronyms, I guess it's SJLJ
From the version number, I would guess you have the official MinGW build, which uses DW2 exception handling.  However, the release (from what I can tell) was built using SJLJ.
Only the plugin
The two exception handling methods cannot be mixed (to my knowledge), so you will either have to compile the plugin using this SJLJ build, or build the whole program with your current compiler.

Offline Taiki

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: Release 12.11 has arrived
« Reply #64 on: January 04, 2013, 11:05:35 pm »
Okay, I'll compile it again then tell you what happen, but I won't have access to my laptop with ICC for a week.

Offline Taiki

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: Release 12.11 has arrived
« Reply #65 on: January 16, 2013, 02:07:55 pm »
Hello, the plugin is (finally) compiled but I still get the error:

icl.exe /nologo -Wall -DCURL_STATICLIB  /O1 -Wall -g -DDEBUG    /Idata\lib\include /I"C:\Program Files (x86)\Intel\Composer XE\bin\ia32\Include" /IE:\project\data\lib\include /I"C:\Program Files (x86)\Intel\Composer XE 2013\compiler\include" /I"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\include" /I"C:\Program Files\CodeBlocks\MinGW\include"  /c "D:\project\AES-rjindael.c" /Fo"D:\project\obj\Debug\AES-rjindael.obj"  /Qstd=c99
icl: error #10114: Microsoft Visual C++ not found in path

I customized the line (to add /Qstd=c99), here is it: $compiler /nologo $options $includes /c "$file" /Fo"$file_dir\$object"  /Qstd=c99.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11939
    • Travis build status
Re: Release 12.11 has arrived
« Reply #66 on: January 16, 2013, 02:11:01 pm »
What is the command executed on the command line which can be used successfully to build the code?

I customized the line (to add /Qstd=c99), here is it: $compiler /nologo $options $includes /c "$file" /Fo"$file_dir\$object"  /Qstd=c99.
This it pretty much the most wrong way to do it. Use the other options in your project's build options or in the compiler's settings.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Taiki

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: Release 12.11 has arrived
« Reply #67 on: January 16, 2013, 02:17:13 pm »
What is the command executed on the command line which can be used successfully to build the code?

I customized the line (to add /Qstd=c99), here is it: $compiler /nologo $options $includes /c "$file" /Fo"$file_dir\$object"  /Qstd=c99.
This it pretty much the most wrong way to do it. Use the other options in your project's build options or in the compiler's settings.
The line work on the ICC command line utility but the path is different: http://pastie.org/private/0q2gx3zgm9vo8h1bifp0g

I guess but actually, as I only use c99, I thought it was a good way not to have to set it on every single project I already have.

Offline Alpha

  • Developer
  • Lives here!
  • *****
  • Posts: 1513
Re: Release 12.11 has arrived
« Reply #68 on: January 16, 2013, 03:24:19 pm »
I forgot to mention that the auto-detect algorithm must be re-run.  Could you try starting with a new config file (so none of your old settings potentially interfere), and then post what is generated for the additional/extra paths for ICC?

Offline Taiki

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: Release 12.11 has arrived
« Reply #69 on: January 16, 2013, 03:38:24 pm »
Remove what is stored in AppData/ is enough to reset prefs?
Also, how to get CB console PATH? Is it the same than the default system PATH?

Edit: Did it, the default path is incorrect for my ICC install (C:\Program Files (x86)\Intel\Composer XE\bin\ia32 on the last version) and I still get the error
« Last Edit: January 16, 2013, 03:45:13 pm by Taiki »

Offline Alpha

  • Developer
  • Lives here!
  • *****
  • Posts: 1513
Re: Release 12.11 has arrived
« Reply #70 on: January 16, 2013, 03:44:22 pm »
Remove what is stored in AppData/ is enough to reset prefs?
Yes.

Also, how to get CB console PATH? Is it the same than the default system PATH?
Code::Blocks modifies the path; you can check what it is by adding a pre/post-build step that prints out the path.

Offline Taiki

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: Release 12.11 has arrived
« Reply #71 on: January 16, 2013, 03:46:17 pm »
Did it, the default path is incorrect for my ICC install (C:\Program Files (x86)\Intel\Composer XE\bin\ia32 on the last version) and I still get the error.
In a cmd.exe, the path didn't changed

Offline Alpha

  • Developer
  • Lives here!
  • *****
  • Posts: 1513
Re: Release 12.11 has arrived
« Reply #72 on: January 16, 2013, 08:22:17 pm »
Oh... you are on 64 bit.

There are some auto-detection flaws in ICC that will take some time (and trial/error) to fix.  Meanwhile, the attached patch might resolve your problem (if you would like to try it).

Offline Taiki

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: Release 12.11 has arrived
« Reply #73 on: January 16, 2013, 09:59:54 pm »
I did but I keep getting the same error =/
I'll try to set the ICC path in the global path and tell if it fix the issue.
If you want to add some extra log to help you to fix it, feel free to do so.
Also, we could continue this discussion via email/somewhere else to stop to flood this release topic ^^'
« Last Edit: January 16, 2013, 10:02:07 pm by Taiki »

Offline Alpha

  • Developer
  • Lives here!
  • *****
  • Posts: 1513
Re: Release 12.11 has arrived
« Reply #74 on: January 17, 2013, 12:04:18 am »
@Admins: Could these ICC posts be split into a separate thread please?