Labels

Android (1) bash (2) boost (2) C (34) C++ (2) cheatsheet (2) CLion (6) css (3) Debian (33) DL (17) Docker (1) Dreamweaver (2) Eclipse (3) fail2ban (4) git (5) GitHub (4) Hacking (3) html (8) http (1) iOS (1) iPad (1) IRC (1) Java (30) javascript (3) Linux (164) Mac (19) Machine Learning (1) mySQL (47) Netbeans (4) Networking (1) Nexus (1) OpenVMS (6) Oracle (1) Pandas (3) php (16) Postgresql (8) Python (9) raid (1) RedHat (14) Samba (2) Slackware (45) SQL (14) svn (1) tar (1) ThinkPad (1) Virtualbox (3) Visual Basic (1) Visual Studio (1) Windows (2)

Thursday 22 October 2020

To change Netbeans C++ binary output location

RIGHT-CLICK PROJECT

PROJECT PROPERTIES > LINKER > GENERAL > OUTPUT


Additionally, if developing on a remote host, the source paths must be mapped unless we are using the configuration as below;


For Access Project files Via, choose SFTP or automatic, this will prevent having to map source folders. I believe the other option doesn't work on Dalzell's servers.

It's also worth noting that when choosing either of the above methods, the source files will be in a .netbeans directory under your the home directory and can be quite long depending on the local source files location, but choosing a sensible binary output location as per the 1st item in this post will pretty much negate this as a real issue  and not to mention that the source files for the projects should be stored locally anyway.

 

For Dalzell, we checkout the project via subversion and save it locally.

We then choose the Build Host as below;





No comments:

Post a Comment

Note: only a member of this blog may post a comment.