Could someone expand on the bullet point: "always have one free core of parallel builds". Does this mean that even if I manually specify C::B to use one thread per core, it will only use N-1 cores? Or does this only apply to the default parallel build settings?The log shows work in progress.
When executing a make uninstall, some folders remain :There is/was a discussion about that: http://www.mail-archive.com/automake@gnu.org/msg00423.html
/usr/local/share/codeblocks/ (with folders inside)
/usr/local/include/[codeblocks | wxsmith | wxSmithContribItems]/
/usr/local/lib/[codeblocks | wxSmithContribItems]
$(HOME)/.codeblocks isn't removed, perhaps this is the expected result ?
But for folders in /usr/loca, this is normal ?
(all this is true for svn 6838, currently compiling 6840).
because VC doesn't work, when the option is !=1.Works well for me, which your OS? VC version?
Loaden: VC 10 is something like VisualStudio 4.0, because VisualStudio 6.0 has compiler with version 12.00.VC10 I think is Visual C++ 2010.
That's my meaning. :lol:Loaden: VC 10 is something like VisualStudio 4.0, because VisualStudio 6.0 has compiler with version 12.00.VC10 I think is Visual C++ 2010.
By the way is it possible to make this option per compiler?U can add new build targets and assign different compiler to them.
On windows if you have gcc and visual studio, you have to modify it when switching compilers,
because VC doesn't work, when the option is !=1.
Launching tool 'Build': /usr/bin/konsole --hold --workdir /mnt/[...]/PAR/src/ -e build.sh (in /mnt/[...]/PDTLIB/src/)Why didn't in work correctly ?? --workdir is a valid switch... http://www.digipedia.pl/man/doc/view/konsole.1/
I think there are two buttons on the right side -> "up" and "down"thanks! I have used codeblocks for about 2 years without noticing it,
I think I found a bug.
Let's say I have a workspace and it is opened, there are 2 projects (regular C). Names are: Project1, MyLibrary.
Project1 uses some functions from MyLibrary.
I opened a C file from Project1, then right clicked on a function (which can be found within Project1), and select 'Find implementation...', and it jumps right to the implementation of that particular function.
BUT, if I do the same (right click and select 'Find impl..') on a function which can be found in MyLibrary it says "Not found <function name>".
And if I jump to project MyLibrary and try to "Find" that function within this project then everything will be fine. But, again, if I try to find a function "outside" this project then I get a message "Not found ... " :(
If I do the same procedures with 'Find declaration ...' then everything is just fine.
It did work fine with other CodeBlocks builds, but last 2 or 3 beta builds don't work fine.
Or maybe I'm wrong and I need to turn on some special features.
Ideas/comments?
You should use two targets, but not two projects.I think I found a bug.
Let's say I have a workspace and it is opened, there are 2 projects (regular C). Names are: Project1, MyLibrary.
Project1 uses some functions from MyLibrary.
I opened a C file from Project1, then right clicked on a function (which can be found within Project1), and select 'Find implementation...', and it jumps right to the implementation of that particular function.
BUT, if I do the same (right click and select 'Find impl..') on a function which can be found in MyLibrary it says "Not found <function name>".
And if I jump to project MyLibrary and try to "Find" that function within this project then everything will be fine. But, again, if I try to find a function "outside" this project then I get a message "Not found ... " :(
If I do the same procedures with 'Find declaration ...' then everything is just fine.
It did work fine with other CodeBlocks builds, but last 2 or 3 beta builds don't work fine.
Or maybe I'm wrong and I need to turn on some special features.
Ideas/comments?
I have noticed this too, indeed this is a nasty problem.
I think this showed up during all the code completion refactorings. Let's hope our CC gurus put their brains too it.
You should use two targets, but not two projects.Can you explain more? What should I do?
Because now a project per a parser.
<Add directory="$(#wx.include)" />
<Add directory="$(#wx)\contrib\include" />
<Add directory="$(#wx)\lib\vc_lib\mswd" />cl.exe - Unable To Locate ComponentThen I have to OK this dialog, and everything is apparently working, including compilation and linking.
This application has failed to start because mspdb80.dll was not found. Re-installing the application may fix this problem.
OK
Some general observations.
To me this reduced functionality has been troublesome ;-) , but don't forget we did get a lot of improvements on the code completion side in return. So please, pretty please, can we take this one 1 step further on the ladder of improved completion ?Here is an un-complete patch for this issue.