Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

An option to clean a non-project, just a file?

(1/2) > >>

m00:
When I wanted to open or create a new file, not a project. I would like to know if it is possible to clean when I use the "Compile current file"? Clean to remove the binary and *.o files.

foo <-- delete (clean)
foo.c
foo.o <-- delete (clean)

Thanks.

rickg22:
Please submit a feature request at our sourceforge page. Thank you :)

m00:
Ok, it means that this feature is not in C::B yet and I will submitting a request. Thanks.

grv575:
Isn't that extra clutter for the menus?

Shouldn't the default behavior of compile current file instead be changed to first remove file.o and then compile?  It's only 1 file so no gain from build management (incremental compilation) and I'm sure if file.o exists and the user hit compile they are expecting to recompile, not get a message saying project is up to date (usually).  Maybe then change the name to build current file or...?

What are people thoughts on this one (know full well this could be 'holy war' type preference but just curious about what the behavior most people agree on)?

mandrav:
Revision 1610 implements "Build", "Build and run", "Run", "Rebuild" and "Clean" compiler actions for single files (without project).

Navigation

[0] Message Index

[#] Next page