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.
Intermediate and target folder changes may be needed for accomodating Netbeans directory structure to a team-defined directory structure. Ex., if the team require intermediate files to be kept in the 'garbage' directory, there's no way to do it. I couldn't find a way to change CND_DISTDIR or CND_BUILDDIR variables. There's only a chance to use them for post-build steps, where copying and moving can be implemented. Nevertheless, it isn't convinient. Thus for now the only way to do it is using external Makefile. P.S. Generally my team uses the following directory structure: bin/$(target_system)/$(binary) - binary executables if any. project/$(build_system)/$(project_files) - project corresponding to a particular build system, ex., MS Visual Studio, GNU Make, or TI Code Composer. doc - component documentation. garbage - temporary build files. include - headers exported by component. lib/$(target_system/$(library) - output libraries if any. src - source files of the component. ut_src - unitest source files. Pretty much 'hacking' is needed to make Netbeans work with such a structure. And no way for now to set target or intermediate directory.
Vladec, you can put the re-definition of the CND_BUILDDIR variable at the end of the Makefile (after inclusion of other mk files) Like: CND_BUILDDIR=garbage Will this help in your situation?
(In reply to comment #1) > Vladec, > > you can put the re-definition of the CND_BUILDDIR variable at the end of the > Makefile (after inclusion of other mk files) > > Like: > > CND_BUILDDIR=garbage > > Will this help in your situation? In fact I didn't want to use any Makefiles while using IDE. The request was targeted to non-Makefile projects. There was no way to change intermediate and target folders through UI. Actually it was so long time ago, that I've already forgotten about my request :)
Yep.. sorry that this was left without an attention from our side... But it's not that much 'hacking' for achieving the needed behavior, isn't it? ;)
Andrew, if I change the makefile, then use the specified folder. it feels good. but not all is well. I design static library, and Application project that uses a static library. when specifying the dependence of the second draft of the first, or by specifying the first project in the list of libraries, the option added original path. and in the generated makefile uses it without the possibility of change.