Maybe it's just me, but...
When you have a D project that consists of a main .d source file and separate .d modules, it would be great if pressing `Build` for the main file would automatically detect the other files, like so:
`dmd main.d module01.d module02.d module03.d`
...which works if you just use the command line. So in Geany, there could be a list of files that it keeps handy to check what the programmer has for files, and then immediately take all the necessary steps to build. Kind of like using the `-I` switch to import? But only now it checks by itself.
Good idea or not?
Or is it already possible within Geany?
Regards, Brendan
On Tue, 9 Sep 2008 14:37:07 +0200 Brendan brenzie@gmail.com wrote:
Maybe it's just me, but...
When you have a D project that consists of a main .d source file and separate .d modules, it would be great if pressing `Build` for the main file would automatically detect the other files, like so:
`dmd main.d module01.d module02.d module03.d`
...which works if you just use the command line. So in Geany, there could be a list of files that it keeps handy to check what the programmer has for files, and then immediately take all the necessary steps to build. Kind of like using the `-I` switch to import? But only now it checks by itself.
Well, Geany's philosophy is not to try to build projects, as for different filetypes and different projects this can be quite complex. We suggest using a Makefile in the manual.
But for D, maybe you'd like the Bud tool - I haven't really used it but it should be as simple as setting the build command to:
bud %e
http://www.dsource.org/projects/build
Also for projects, only make in base path is implemented as an extra build option - so in this case you could have a Makefile in the project base path:
all: <TAB>bud my_app_name
Then you could use the Make command for whatever the current file is.
Regards, Nick
Yes, that's true. But I don't trust programs like Bud, Rebuild, and DSSS. I don't know, it's just that I had some bad experiences with it in the past. But maybe I should try it again.
Regards
On 09/09/2008, Nick Treleaven nick.treleaven@btinternet.com wrote:
On Tue, 9 Sep 2008 14:37:07 +0200 Brendan brenzie@gmail.com wrote:
Maybe it's just me, but...
When you have a D project that consists of a main .d source file and separate .d modules, it would be great if pressing `Build` for the main file would automatically detect the other files, like so:
`dmd main.d module01.d module02.d module03.d`
...which works if you just use the command line. So in Geany, there could be a list of files that it keeps handy to check what the programmer has for files, and then immediately take all the necessary steps to build. Kind of like using the `-I` switch to import? But only now it checks by itself.
Well, Geany's philosophy is not to try to build projects, as for different filetypes and different projects this can be quite complex. We suggest using a Makefile in the manual.
But for D, maybe you'd like the Bud tool - I haven't really used it but it should be as simple as setting the build command to:
bud %e
http://www.dsource.org/projects/build
Also for projects, only make in base path is implemented as an extra build option - so in this case you could have a Makefile in the project base path:
all: <TAB>bud my_app_name
Then you could use the Make command for whatever the current file is.
Regards, Nick _______________________________________________ Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On Tue, 9 Sep 2008 19:34:09 +0200 Brendan brenzie@gmail.com wrote:
Yes, that's true. But I don't trust programs like Bud, Rebuild, and DSSS. I don't know, it's just that I had some bad experiences with it in the past. But maybe I should try it again.
Fair enough. Maybe project management & building could be improved, but for the core of Geany it should be a general feature, not one that knows anything about any particular language/compiler.
Regards, Nick
On 11/09/2008, Nick Treleaven nick.treleaven@btinternet.com wrote:
On Tue, 9 Sep 2008 19:34:09 +0200
Brendan brenzie@gmail.com wrote:
Yes, that's true. But I don't trust programs like Bud, Rebuild, and DSSS. I don't know, it's just that I had some bad experiences with it in the past. But maybe I should try it again.
Fair enough. Maybe project management & building could be improved, but for the core of Geany it should be a general feature, not one that knows anything about any particular language/compiler.
Regards, Nick
Sounds good :)
What about something like having a particular project window, a very simple one, where the user can set which files or folders to import/include?
On Thu, 11 Sep 2008 17:19:24 +0200 Brendan brenzie@gmail.com wrote:
What about something like having a particular project window, a very simple one, where the user can set which files or folders to import/include?
Not sure how this would work - do you mean extra flags/files to append to the build command?
Regards, Nick
On 12/09/2008, Nick Treleaven nick.treleaven@btinternet.com wrote:
On Thu, 11 Sep 2008 17:19:24 +0200
Brendan brenzie@gmail.com wrote:
What about something like having a particular project window, a very simple one, where the user can set which files or folders to import/include?
Not sure how this would work - do you mean extra flags/files to append to the build command?
Something like that. The program would read what files the user specifies
in the window, then the program puts them in the build command (but that's of course what the user doesn't (have to) see).
On Fri, 12 Sep 2008 16:10:25 +0200 Brendan brenzie@gmail.com wrote:
What about something like having a particular project window, a very simple one, where the user can set which files or folders to import/include?
Not sure how this would work - do you mean extra flags/files to append to the build command?
Something like that. The program would read what files the user specifies in the window, then the program puts them in the build command (but that's of course what the user doesn't (have to) see).
I'm not sure about that - I think that would involve implementing workarounds for not writing a Makefile. Say we implemented listing project source files, and you could use that in a build command with something like e.g. %p, next people might request more powerful build features.
Personally I think for portability and for power it's best to use Makefiles, otherwise people need Geany just to build the software. (We could implement a project-specific make command where arguments can be listed, e.g. 'make debug CFLAGS=...'.)
Of course if people want to write plugins/lua scripts to do build management for specific compilers/tools, that's up to them.
Regards, Nick