Re: Complete Guide to Using DLLs in OpenEuphoria
- Posted by ghaberek (admin) Sep 14, 2015
- 2243 views
The only thing missing is in your example is the eu.cfg.
I guess that sort of went without saying. I use eu.cfg a lot. You'd actually need several files, one in each of demo, src, and test to point them all back to include.
I would propose that if you are building a wrapper then your target "audience" is different and they have a different set of concerns. In this case I'm speaking of the difference between writing an application vs writing a library. The problem domain is similar, but not necessarily identical.
Yes and no, I suppose. I look at everything as a project. A library wrapper project should have include (obviously) and probably test for sanity checking. But it might also contain bin for the compiled binaries and maybe src for the original source of the C library. And you'll probably have demos in there, too. So you can see how it all starts to come together. That's what I just did for libxlsxwriter.
I for one would be super excited to see this article. I'm in the process of integrating make into an automated test suite and perhaps a package manager and would love to see your thoughts on using make.
Okay, I will start working on that soon. I already have a lot of notes on the subject but I also have to go through a lot of trial-and-error to get things distilled down for the end-programmer who's not already familiar with make. It's a very dynamic system with rarely a single "right" way to do things.
To be honest, what I'm really doing here is building the basic foundation for the way an IDE or any other build system would manage a project structure. I've taken a lot of cues from other languages and IDEs and I am hopeful that this can become and integral part of the way Euphoria programmers design their applications.
-Greg
