Hmm... On second thought... I think you should probably put some more thought into the linking process before adding more features like this.
You have to remember, there are so many infinite ways that one can link a program or library (dll), that they invented makefiles, and even complete complex build systems and languages just for that purpose. I'm thinking it will be very hard to capture all that functionality in one or more GUI dialogs... Maybe you should do a small study on various build systems (eg, Makefiles, autoconf/automake/libtool, bakefile, scons, jam/bjam, etc,...) and see how they implement these things. You'll find that most use complex scripting or xml (bakefile), to direct the linking process. Capturing all that functionality in a GUI would be great! But it would also very hard to be complete. I think,... to do it 'right', it would require some study.
Of course, you don't HAVE to capture all that functionality, you can always support calling an external build system, and let that take care of the whole thing for you. However, implementing SOME of it, and additionally supporting an external build system may confuse users into thinking that they aren't able to do certain things.
Implementing all of it probably isn't a good idea, since you don't have your entire lifetime to complete this project, nor do you have an entire team of developer slaves.
So maybe you should put some thought into letting an external application direct the linking and compiling process, and drop more features like this all togeather.
Just some thoughts.
You have to remember, there are so many infinite ways that one can link a program or library (dll), that they invented makefiles, and even complete complex build systems and languages just for that purpose. I'm thinking it will be very hard to capture all that functionality in one or more GUI dialogs... Maybe you should do a small study on various build systems (eg, Makefiles, autoconf/automake/libtool, bakefile, scons, jam/bjam, etc,...) and see how they implement these things. You'll find that most use complex scripting or xml (bakefile), to direct the linking process. Capturing all that functionality in a GUI would be great! But it would also very hard to be complete. I think,... to do it 'right', it would require some study.
Of course, you don't HAVE to capture all that functionality, you can always support calling an external build system, and let that take care of the whole thing for you. However, implementing SOME of it, and additionally supporting an external build system may confuse users into thinking that they aren't able to do certain things.
Implementing all of it probably isn't a good idea, since you don't have your entire lifetime to complete this project, nor do you have an entire team of developer slaves.
So maybe you should put some thought into letting an external application direct the linking and compiling process, and drop more features like this all togeather.Just some thoughts.







Amazing isn't it? I should have done this a long time ago.





