Re: [fluid-dev] State of my FluidSynth fork

[Miguel Lobo]

Hi Jimmy and Josh,

Many thanks for your interest!

I have now uploaded the project to SourceForge, here:

https://sourceforge.net/projects/gleamsynth

(The project is called Gleam, but that name was taken in SourceForge
so the page there uses a slightly different name).

It should now be possible to browse the project or check it out using
SourceForge's anonymous SVN access.

There is no documentation at all yet, so here are some quick build instructions:

1. You need Python 2.5, GCCXML 0.7 or later and the current SVN
version of pygccxml.  If you're using Debian, there are packages for
Python and GCCXML, so installing those shouldn't be a problem.  As for
pygccxml, you can check it out from their SVN repository here:
http://sourceforge.net/svn/?group_id=118209 and then follow their
installation instructions.

2. If g++ points to GCC 4.1 or earlier in your system, you can now run
the following command on Gleam's main directory:

python build.py

This should build Gleam.

3. GCCXML doesn't work yet with GCC 4.2 or later, so if g++ points to
one of those, you will need to install GCC 4.1 too.  After you've done
that, assuming the g++ executable for GCC 4.1 is then called g++-4.1,
you should run:

GCCXML_COMPILER=g++-4.1 python build.py

This is instead of the command suggested in the previous point.

As I said in my previous mail, any comments, questions or suggestions
are quite welcome.

Regards,
Miguel

On Jan 10, 2008 6:13 PM, jimmy <address@hidden> wrote:
>
> --- Josh wrote:
>
> > Hey Miguel,
> >
> > I'd be interested in seeing your port.  Do you have
> > a location to
> > download it from?  As I've mentioned before,
> > FluidSynth itself could use
> > a lot of cleanup for my own willingness to
> > contribute to it.  If for
> > some reason your C++ binding looks like the right
> > direction, it may make
> > sense to use it in FluidSynth itself and provide an
> > older C
> > compatibility binding.  Of course there may still be
> > differences in
> > direction of your project versus FluidSynth, in
> > which case they would
> > remain separate, but it would at least make it
> > easier for the two
> > projects to share changes.
> >
> > Best regards,
> >       Josh
>
> Miguel,
>
> I was waiting for Josh to clear the air first before I
> say something here ;-)  I would be insterested to see
> your code, too.  Whenever you get the time for what
> ever arrangement you want to make, that is.
>
> And thanks,
>
> Jimmy
>
>
>
>
>
>       
> ____________________________________________________________________________________
> Never miss a thing.  Make Yahoo your home page.
> http://www.yahoo.com/r/hs
>
>
>
> _______________________________________________
> fluid-dev mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/fluid-dev
>