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.
I've come across a problem when dealing with windows hooks. (see e.g. http://win32assembly.online.fr/tut24.html for more informations). The thing is I want to write a program, however a part of it must reside in a dll. This way something, what is a single project and not a big one must be divided in two. My vision is - instead of creating a static library project, a dynamic library project or an executable project, just let us create a project with a workspace. The workspace would contain all the source files and any number of user-defined targets. The user could then "assign" sources to targets and those associations would be easily translated into makefile dependencies. Unassigned files would not be compiled, so "exclude from build" option would not be necessary.
Hi, From your description looks like Configurations and Batch build should be OK for you. You can create two different configurations: one for dll (with it's set of included/excluded sources) and other for executable project (with it's set of included/excluded sources). Switching between configurations (combobox on main toolbar) allows quickly navigate between your targets + you will see how some files become "inactive" while other become "active" in the corresponding configuration. Run->Batch Build Project... action allows to build several configurations with one action.
Yes, it works, but from what I have seen (and I've seen little) adding a new file makes it "buildable" in all configurations. A proggrammer needs than to iterate through all of them and exclude the file from building in most of them. Less problem is having double that number of configs - two for every target (Debug and Release). We end up with several configurations which are mostly the same, juxt diffrent files are built. It just seems like a workaround for me.