Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign
CC makes C::B hang in ExpandBackticks
oBFusCATed:
Yes, this message is printed by wxexecute...
Alpha:
--- Quote from: MortenMacFly on January 05, 2013, 07:30:25 am ---Does this one:
--- Quote from: Alpha on January 05, 2013, 04:10:30 am ---Congratulations, you have discovered not one bug, but two! [...]
--- Code: ---Index: src/sdk/compiler.cpp
--- End code ---
--- End quote ---
...make this one:
--- Quote from: jens on January 05, 2013, 02:02:45 am ---Yes, they are caused by the xml compiler code, Alpha can you look at them?
[...]
I suggest catching the error output and either give a more clear error message or just suppress it.
--- Code: ---Index: src/plugins/compilergcc/resources/compilers/options_clang.xml
--- End code ---
--- End quote ---
...obsolete?
--- End quote ---
Yes.
--- Quote from: jens on January 05, 2013, 10:16:32 am ---It will only be visible from a console, but as it is not meant for the user it should be caught (with a wxArrayString) and dismissed.
--- End quote ---
With this patch, it should no longer report it to the console; is it still doing that for you?
My original intention behind
--- Code: ---<if exec="XXX">
--- End code ---
was to allow a conditional to test if a program existed, so in my opinion, there should not be any error message if execution fails.
--- Quote from: oBFusCATed on January 05, 2013, 12:29:37 pm ---Also, this is a real problem because the linking with clang is broken.
--- End quote ---
Clang's linker is not broken (to my knowledge); I had discovered (by accident) that it was possible to install a working Clang without llvm. The conditional is there so that hopefully Clang will "just work" regardless of user configuration.
oBFusCATed:
--- Quote from: Alpha on January 05, 2013, 02:10:00 pm ---Clang's linker is not broken (to my knowledge); I had discovered (by accident) that it was possible to install a working Clang without llvm. The conditional is there so that hopefully Clang will "just work" regardless of user configuration.
--- End quote ---
I've just upgraded to llvm/clang 3.2 and linking .a files doesn't work anymore. With 3.1 all was fine...
Also the problem is that you never check if the cmd[0]=="". As far as I can see your patch doesn't add such checks. Executing ""+" "+"-version" will never be a good idea...
MortenMacFly:
--- Quote from: oBFusCATed on January 05, 2013, 02:25:24 pm ---I've just upgraded to llvm/clang 3.2 and linking .a files doesn't work anymore. With 3.1 all was fine...
--- End quote ---
Which distro do you use (in case its Windows)? I am looking for a working up-to-date distro of Clang for Windows 32.
I used to use this one:
http://www.ishani.org/web/articles/code/clang-win32/
...but it doesn't work anymore on WinXP/32.
Jenna:
The failure message does no longer occur.
I wonder why it was there before.
The bull-logger should have eaten it also I think.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version