Currently, it seems to be impossible to specify the Visual Studio compiler (cl.exe) as the default C++ compiler. Since
we are running a cross-platform project that should run on Linux as well as Windows, support for this compiler would be
Toolchain is not extensible and you should be able to implement a compiler personality for just about any compiler. HowTo should be posted on http://wiki.netbeans.org/CAndCPlusPlus in near future.
I assume that "is not extensible" should be "is now extensible" or something else that makes more sense.
This shouldn't be marked as resolved/fixed unless NetBeans 6.5 sees that the Visual Studio Compiler is installed and automatically configures to use it, or at
least is as simple as selecting Visual Studio from a combobox. This is based on the assumption that manually configuring this stuff will be painful. E.g. I
simply can't get Cygwin to compile any code that calls Win32 APIs - to the point that I don't think Windows should be listed as a supported platform for the
C/C++ development pack.
I still have to check for NetBeans 6.5, but with 6.0 it was impossible to select cl.exe. I made several attempts to
create batchfiles and renaming cl.exe to gcc.exe, but to no avail. After a day of trying I gave up. It looked like the
only workaround was to create a separate executable that calls cl.exe, translating the commandline options and such.
Since I don't have a Windows PC here with NetBeans installed, I cannot test it with 6.5. I'll check that this week at
home, and update this item.
I'll leave this as "RESOLVED FIXED" for now, giving you the benefit of the doubt! ;-)
Here is the HowTo:
That page still lists GNU C/C++ compilers as a requirement (and is therefore unrealistic for the Windows platform).
reopen the issue....
>That page still lists GNU C/C++ compilers as a requirement
It is a requirement for the tutorial.
You can apply the tutorial for cl.exe also.
There is no plan to support cl.exe. There is machinery that enable users to configure it and use on their own risk. We
have no solution for debugging binaries produced by cl.exe.
It would be useful even without debugger support, but I understand the desire to provide something more complete. In
the mean time, please remove the claim that Windows is a supported platform for C/C++ development. Unless someone can
demonstrate compiling typical Windows code using the Windows Platform SDK with the solutions proposed so far. E.g. if
you can build the JRE native components for Windows (AWT, D3D graphics pipeline, etc.) entirely within NetBeans then
you've got a solution.
We have vast majority of users residing on Windows... So, I'd not surprise them with a claim that Windows is not
I'm one of them... and I find the C/C++ support in NetBeans on Windows is lacking. I've spent many hours and I can't
compile my Windows code with NetBeans. (I'm not new to C/C++ development.) GCC can't seem to deal with the Microsoft
headers. Are there Windows users that are producing real-world applications requiring the use of the Windows Platform
SDK, or are they just playing around? If users have solved these issues then their secrets need to be rolled into the
C/C++ NetBeans module so it "just works". Right now getting a Windows configuration that works is pure hell. I'm
trying again with MinGW instead of Cygwin to see if that makes any difference...
resolved in 6.7