This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 158552 - It should be possible to set up remote host without seting remote compiler set
Summary: It should be possible to set up remote host without seting remote compiler set
Status: RESOLVED DUPLICATE of bug 248752
Alias: None
Product: cnd
Classification: Unclassified
Component: Remote (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Vladimir Kvashin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-13 18:58 UTC by Vladimir Kvashin
Modified: 2015-11-24 14:58 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Kvashin 2009-02-13 18:58:39 UTC
Some users need to use remote debugging, without building their applications. However, current remote development design
makes this impossible. This is not correct.

Here is a citation from such user' letter
> I am working with an ARM cross compiler and am trying to remote debug to an embedded ARM based target. 
> The target has no compiler sets available but supports GDB. 
> Currently the target is simulated using the Qemu emulator. 
> However i can not seem to get beyond the "Add new tool collection for xxx" dialog.
Comment 1 Vladimir Kvashin 2009-02-13 19:21:39 UTC
I probably didn't state the issue accurate enough. 
Compilers may present on remote machine, but can not be recognized by NetBeans IDE.
The project still can be built if it is based on the user-written makefile.
NetBeans should make possible to work remotely in such case too.

Comment 2 Maria Tishkova 2009-05-21 15:34:29 UTC
in next release
Comment 3 Alexander Pepin 2010-03-26 15:49:39 UTC
it's rather an enhancement
Comment 4 Alexander Simon 2015-11-24 09:25:06 UTC
Was it fixed in bug #248752?
Comment 5 Vladimir Kvashin 2015-11-24 14:58:07 UTC
Exactly. Thank you!

*** This bug has been marked as a duplicate of bug 248752 ***