Your wishes for next release of CND

[charlls]

there is definitely a way to upgrade to gcc 4.x in solaris:

http://www.opencsw.org/packages/CSWgcc4g++/

[mrvolleyball]

Keep up the good work , I've started to like many things about Netbeans for C++. Here are my suggestions and issues I've encountered with it:

Parsing
------------------------------------------
1) The code completion related parsing gets in the way occasionally and effectively blocks development until it completes. It would be much more usable if this parsing occurred on a background thread so it didn't interfere with GUI events.

2) I now have a faster machine so this doesn't affect me anymore but: The parsing seems resource intensive and can cripple a machine to the point of rendering the IDE useless. A switch to disable parsing or (1) would be good.

CMake integration:
------------------------------------------
I've been using Netbeans for C++ with CMake projects on Linux and I've noticed some related things which I have found workarounds for but are a bit awkward.

Given: A directory structure with a root, level 1, and level 2 directories. CMake files exist at every level. Projects exist at level2. Building everything via the root cmake file (i.e. cmake .; make) from the command line is successful.

Issues:
1) I use the "create group" feature based on a directory containing projects to automatically load all the projects into the IDE. Afterwards I've found no easy way to build all the projects. I see how to build projects individually and where the make files have dependencies these dependencies get built as well. To work around this I do such things from the command line.

2) Although the make files contain all the necessary include directories, I must add them to (tools -> options -> C++ -> include directories) in order for the IDE's code completion to work properly.

3) Defines specified in the make files don't seem to be noticed by the code completion. For example I had DEBUG in the make files but had to manually add it to the IDE to be defined for code completion (tools -> options -> C++ -> macro definitions)

Remote development:
--------------------------------------
1) Remote building seems much slower than local building. So slow in fact that I've decided not to use it for now (maybe 5-10 times slower is my guess). If it were not so slow it'd be a great feature for me.

2) I tried working around (1) by checking out the code on the remote machine into the directory structure generated by (1). My thought was to do a full remote build via command line and then use the remote development functionality via Netbeans. However, this did not work because the remote development functionality was synchronizing the files in a binary format on the remote side and this obviously confused the source control system. I've instead used a remote desktop solution with netbeans installed on the remote machine which is cumbersome.

[mrvolleyball]

Another item I forgot to mention

Remote development:
--------------------------------------
3) I've been doing out of source builds and the Remote development solution seemed confused by this. When I initially set it up the build would fail. This is part of what sent me on the tangent described in (2) which allowed the build to succeed but the binary files created by Netbeans to synchronize changes caused confusion that would kill the build. It's possible I was missing some prescribed way of making this work, but that's my 2cents.

[Vladimir Kvashin]

Hi,

I'm responsible for remote development. Thank you for letting me know
your issues.

I'd love to fix issues you mention. But let me first propose you a
better workaround.
There are two command line options:

1) -J-Dcnd.remote.scp=true
allows to select more synchronization options in Host Properties dialog
(or when setting up a host)
Try selecting SFTP. Although not officially supported, it seems to works
ok and will probably suit you better.

2) -J-Dcnd.remote.sync.project.action=true
If set, an action "Upload to user@host" appears on folders in Projects Pane.
You can then use this action to manually upload your sources.

Could you please try and tell me
- whether (1) makes your build faster
- does manual upload take long?

Thank you,
Vladimir


On 03/01/2011 05:48 PM, mrvolleyball wrote:

[Vladimir Voskresensky]

Hi, mrvolleyball

Thanks for all your feedback.
Could I ask you and try NB 7 Beta 2 and confirm if issues from Parsing
section are still in place or they are resolved.

Btw, about extracting settings from makefile.
If you can build from IDE => after Clean&Build action you will see in
Output window an icon which allow you to configure code assistance based
on make log => compiler options should be extracted and put into your
project files.

Thanks!
Vladimir.

On 03/01/2011 05:48 PM, mrvolleyball wrote:

[mrvolleyball]

Thanks Vladimir,

I'll give your suggestions a try soon when I have some spare cycles.

[romulus]

[mrvolleyball]

Per Vladimir's suggestion I tried to give remote debbuging a try in NB 7.0 RC1. However, I was having difficulties.

I create a new thread for my issues here:
http://forums.netbeans.org/viewtopic.php?t=38083&start=0&postdays=0&postorder=asc&highlight=

[wholesale NFL jerseys]

thank you for sharing .