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.
This was brought up while Cadence visits. When new project is created from existent code... - 'Working directory' - not clear what does this mean; - Once directory is selected, default is set to 'Automatic' configuration and 'Finish' button is active. Nobody reads what is written and it is *absolutely* unexpected that IDE starts make clean; make all. As it uses wrong make (not clearmake in this case), this means that it just removes binaries and user has to re-build a project again (which may take a while).. - Another scenario (need to reproduce) - creating project from existent sources; Only sources directory is specified; There are several binaries in (sub)directories of the specified folder. They are built for different platforms; [Looks like] when binaries were analyzed, wrong binaries were taken. At lease code assistance was configured so that some includes were taken for Linux, while we were on Solaris (still linux headers were accessible from it with the same path as on original Linux) - When use 'advanced' mode, the last step is to select build result. Default filter (elf files) filters-out .so files (while they are elf files) - they are not visible in the chooser. - After project creation we always saw a notification with a warning that project was created successfully, but there were some problems with code assistance. But the information is ambiguous. It says: (OK sign) Project was successfully created (Not-OK Sign) There were problems with code-assistance 0 out of 36 source files have limited <something> 0 out of 15 header files have limited <something>