Re: [Gambas-devel] gbmake. A drop-in replacement to automake
Brought to you by:
gambas
From: Sebastian K. <se...@gm...> - 2012-09-14 21:40:49
|
On Fri, Sep 14, 2012 at 3:52 PM, Tobias Boege <to...@ga...> wrote: >> I just created a branch so we could test this new implementation. I >> didn't wanted to pollute trunk with 3.3 this close. >> >> With the build structure i used, and how libraries are implemented, i >> believe a more simple approach to the symlinked module would be to add >> the gbm3 tool as a library (or component, i'm not sure) to the ide. >> The install path will be known, as the gbx3 executable should be in >> the same directory. What do you think of this? > > I just arrived at home again and I am apparently not up-to-date with this > project. Does this mean that we cannot use gbm3 outside gambas3 - even > though it has to have much less dependencies? > Personally, I would prefer a stand-alone program - be it cobbled together > from symlinked sources, or whatever - over an integrated library, because > this way I could actually compile and use it. > Right now, it only depends on the interpreter, and is compiled just after it. You can check my branch at the svn repository. To test it, i implemented it to install every gambas component under comp/, so any bug should be easy to spot. If you follow the thread you will see that i decided to let the packaging alone for now. With that out, there is a really small amount of code that needs to be shared. In reality, my idea was just to abstract the installation of a project, which right now is the only part of the development process of a gambas app that in not standardized inside a specific tool, but if i really wanted to make that process simple enough, i also had to implement the compilation (gbx3) and packaging (gba3) of a project. I have not tested a more "native" solution, although my language of choice would have been python 3.x, nothing more native than gambas would be, plus, it integrates pretty well. > You wanted thoughts - it's your work thus your decision (at least not mine). If i thought like this, i would have worked it out everything locally, uploaded it once it was finished, and let it "shine". I shared it because A. there are some parts of the gambas ecosystem that i don't know, and are needed to completely integrate this tool, and B. it's better when there is more than one dev working alone. Feel free to commit, rewrite, refactor, rework, etc. > > Regards, > Tobi > > > ------------------------------------------------------------------------------ > Got visibility? > Most devs has no idea what their production app looks like. > Find out how fast your code is with AppDynamics Lite. > http://ad.doubleclick.net/clk;262219671;13503038;y? > http://info.appdynamics.com/FreeJavaPerformanceDownload.html > _______________________________________________ > Gambas-devel mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gambas-devel |