wavepacket-ng-devel

[Wavepacket-ng-devel] Build system

[Ulf L. <ul...@wa...>]

Hi,

what we further need to decide on is a build system. I have some
limited knowledge, maybe someone of you can contribute here.

The program will consist of different libraries, each being a more
or less separate project with different dependencies. It would make
sense, for example, to put the mathematical stuff in a separate
library, so that we can have, e.g., a simple mathematics library with
few dependencies and, say, another library that uses Cuda for more
speed, but with exotic dependencies.

So what we make is first basic make tool, and second a mechanism for
dependency recognition.

What I know of make tools is
* make (ugly in some parts, but pretty standard on Unix)
* ant (Java-based and thus portable)
* maven (only heard of it; sounds nice, but no knowledge)
Do you have deeper knowledge or know other build toold, and/or what
would you suggest to use?

For the dependency recognition, what I know here is:
* Do everything as variables. The user then has to edit the "Makefile"
  and compile
* autoconf/automake. Pretty standard, but really ugly as far as I
  recall.
* CMake. I know it exists, but have never used it.
* others?
What ideas, suggestions do you have here?

Ulf

[Wavepacket-ng-devel] Build system

[Ulf L. <ul...@wa...>]

Hi,

to simplify the installation of the Wavepacket library, I have put
together a virtualization image that hopefully installs all
dependencies more or less out of the box.

I tried to simplify the installation process as much as possible; the
result can be found under
http://sourceforge.net/p/wavepacket/cpp/wiki/VirtualMachine/

If you want to try out the C++ version of Wavepacket and have not
managed to get it compiled yet, this hopefully provides a simple enough
way to do so. If you do try it out, I would be happy if you could
report any errors, problems, or inconsistencies and bad explanations in
the documentation.


Ulf

Re: [Wavepacket-ng-devel] Build system

[Ulf L. <ul...@wa...>]

Since the build system can be migrated rather easily, does anyone mind
if we start with simple makefiles?


Ulf


On Wed, 5 Dec 2012 23:25:23 +0100
Ulf Lorenz <ul...@wa...> wrote:

> Hi,
> 
> what we further need to decide on is a build system. I have some
> limited knowledge, maybe someone of you can contribute here.
> 
> The program will consist of different libraries, each being a more
> or less separate project with different dependencies. It would make
> sense, for example, to put the mathematical stuff in a separate
> library, so that we can have, e.g., a simple mathematics library with
> few dependencies and, say, another library that uses Cuda for more
> speed, but with exotic dependencies.
> 
> So what we make is first basic make tool, and second a mechanism for
> dependency recognition.
> 
> What I know of make tools is
> * make (ugly in some parts, but pretty standard on Unix)
> * ant (Java-based and thus portable)
> * maven (only heard of it; sounds nice, but no knowledge)
> Do you have deeper knowledge or know other build toold, and/or what
> would you suggest to use?
> 
> For the dependency recognition, what I know here is:
> * Do everything as variables. The user then has to edit the "Makefile"
>   and compile
> * autoconf/automake. Pretty standard, but really ugly as far as I
>   recall.
> * CMake. I know it exists, but have never used it.
> * others?
> What ideas, suggestions do you have here?
> 
> Ulf
> 
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add
> services Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Wavepacket-ng-devel mailing list
> Wav...@li...
> https://lists.sourceforge.net/lists/listinfo/wavepacket-ng-devel

Re: [Wavepacket-ng-devel] Build system

[Andrea at d. <me...@an...>]

Hi,

I think that Makefile is a good starting point. Not sure but it's easily
create a "Makefile project from Existing Code" under Eclipse C/C++

Andrea

On Sun, Dec 16, 2012 at 11:04 PM, Ulf Lorenz <ul...@wa...> wrote:

> Since the build system can be migrated rather easily, does anyone mind
> if we start with simple makefiles?
>
>
> Ulf
>
>
> On Wed, 5 Dec 2012 23:25:23 +0100
> Ulf Lorenz <ul...@wa...> wrote:
>
> > Hi,
> >
> > what we further need to decide on is a build system. I have some
> > limited knowledge, maybe someone of you can contribute here.
> >
> > The program will consist of different libraries, each being a more
> > or less separate project with different dependencies. It would make
> > sense, for example, to put the mathematical stuff in a separate
> > library, so that we can have, e.g., a simple mathematics library with
> > few dependencies and, say, another library that uses Cuda for more
> > speed, but with exotic dependencies.
> >
> > So what we make is first basic make tool, and second a mechanism for
> > dependency recognition.
> >
> > What I know of make tools is
> > * make (ugly in some parts, but pretty standard on Unix)
> > * ant (Java-based and thus portable)
> > * maven (only heard of it; sounds nice, but no knowledge)
> > Do you have deeper knowledge or know other build toold, and/or what
> > would you suggest to use?
> >
> > For the dependency recognition, what I know here is:
> > * Do everything as variables. The user then has to edit the "Makefile"
> >   and compile
> > * autoconf/automake. Pretty standard, but really ugly as far as I
> >   recall.
> > * CMake. I know it exists, but have never used it.
> > * others?
> > What ideas, suggestions do you have here?
> >
> > Ulf
> >
> >
> ------------------------------------------------------------------------------
> > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> > Remotely access PCs and mobile devices and provide instant support
> > Improve your efficiency, and focus on delivering more value-add
> > services Discover what IT Professionals Know. Rescue delivers
> > http://p.sf.net/sfu/logmein_12329d2d
> > _______________________________________________
> > Wavepacket-ng-devel mailing list
> > Wav...@li...
> > https://lists.sourceforge.net/lists/listinfo/wavepacket-ng-devel
>
>
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Wavepacket-ng-devel mailing list
> Wav...@li...
> https://lists.sourceforge.net/lists/listinfo/wavepacket-ng-devel
>



-- 
"Experience is what you get when you don't get what you want", Dan Stanford

Andrea Girardi
blog: http://www.andreagirardi.it
linkedin: http://www.linkedin.com/in/andreagirardiverona
web http://www.agdev.net

Re: [Wavepacket-ng-devel] Build system

[Ulf L. <ul...@wa...>]

On Mon, 17 Dec 2012 09:54:09 +0100
Andrea at dotIT <me...@an...> wrote:

> Hi,
> 
> I think that Makefile is a good starting point. Not sure but it's
> easily create a "Makefile project from Existing Code" under Eclipse
> C/C++

Ok, no more contributions, so I would consider this settled as well.

As a side remark, I am just trying to customize the source forge
tracker. We will see how this turns out.


Ulf,
as usual busy