Glasgow development

Hi,

I am a programmer and amateur photographer who is interested
in helping with
Glasgow development on Linux.  I have been a professional
software developer
for about 7 years with a variety of languages, including
C++.  My first goal is
to get a working Glasgow build, but I can't find any
working Makefiles,
automake / autoconf files, or instructions on where to
start.  Can anyone help?
After that, I would like to start with bug fixes to get my
feet wet.

-- 
-Chris McKinley


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Cinepaint-developers mailing list
Cinepaint-developerslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ci
nepaint-developers

Chris,

Welcome on this mailing list.
Thanks for your great offer.

Tom Huffmann prepared something for inclusion into the
Glasgow tree. It is 
about the PMK build package. See:
http://so
urceforge.net/tracker/index.php?func=detail&aid=1295964&
amp;group_id=75029&atid=542708

PMK was been in the talk because of its simplisity in
contrast to 
autotools. To find a maintainer for autotools was rather
hard.


Nethertheless, if you like autotools and are familiar with,
you are 
welcome to use it.


kind regards
Kai-Uwe Behrmann
                                + development for color
management 
                                + imaging / panoramas
                                + email: ku.bgmx.de
                                + http://www.behrmann.name


Am 17.07.06, 15:23 -0500 schrieb Chris McKinley:

> Hi,
> 
> I am a programmer and amateur photographer who is
interested in helping with
> Glasgow development on Linux.  I have been a
professional software developer
> for about 7 years with a variety of languages,
including C++.  My first goal is
> to get a working Glasgow build, but I can't find any
working Makefiles,
> automake / autoconf files, or instructions on where to
start.  Can anyone help?
> After that, I would like to start with bug fixes to get
my feet wet.
> 
> -- 
> -Chris McKinley
> 

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Cinepaint-developers mailing list
Cinepaint-developerslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ci
nepaint-developers

Kai,

I see the pmk tar file, and have built it, but there isn't
a pmk file
available.  I would be happy to start by working on getting
it building under
whatever build system, but I don't know what the
dependencies are, or what
needs to be built.  I can probably figure some of this out,
but it would
take a lot less time to get this going if there were a list
of what the
requirements are and what in general each subdirectory
produces.  Can you help
me get this information?

Thanks,

-- 
-Chris McKinley

On Thu, Jul 20, 2006 at 12:35:43AM +0200, Kai-Uwe Behrmann
wrote:
> Chris,
> 
> Welcome on this mailing list.
> Thanks for your great offer.
> 
> Tom Huffmann prepared something for inclusion into the
Glasgow tree. It is 
> about the PMK build package. See:
> http://so
urceforge.net/tracker/index.php?func=detail&aid=1295964&
amp;group_id=75029&atid=542708
> 
> PMK was been in the talk because of its simplisity in
contrast to 
> autotools. To find a maintainer for autotools was
rather hard.
> 
> 
> Nethertheless, if you like autotools and are familiar
with, you are 
> welcome to use it.
> 
> 
> kind regards
> Kai-Uwe Behrmann
>                                 + development for color
management 
>                                 + imaging / panoramas
>                                 + email: ku.bgmx.de
>                                 + http://www.behrmann.name
> 
> 
> Am 17.07.06, 15:23 -0500 schrieb Chris McKinley:
> 
> > Hi,
> > 
> > I am a programmer and amateur photographer who is
interested in helping with
> > Glasgow development on Linux.  I have been a
professional software developer
> > for about 7 years with a variety of languages,
including C++.  My first goal is
> > to get a working Glasgow build, but I can't find
any working Makefiles,
> > automake / autoconf files, or instructions on
where to start.  Can anyone help?
> > After that, I would like to start with bug fixes
to get my feet wet.
> > 
> > -- 
> > -Chris McKinley
> > 
> 
>
------------------------------------------------------------
-------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get
the chance to share your
> opinions on IT & business topics through brief
surveys -- and earn cash
> http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Cinepaint-developers mailing list
> Cinepaint-developerslists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ci
nepaint-developers
> 


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Cinepaint-developers mailing list
Cinepaint-developerslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ci
nepaint-developers

Chris,

What I have is a older CVS snapshot before the last great
code 
reorganisation. There you can have a look at the various
file 
dependencies at time :
http://www.behrmann.n
ame/index.php?option=com_weblinks&task=view&catid=67
&id=93
There is no top source dir build. It would be nice to
configure some 
options on top and then let make walk in the apropriate
directories.
The glasgow directory holds the autotooled GUI. 


A pmk file is not available. It would have to be created
from scratch.

Dont miss:
http://cinepaint.bigasterisk.com/GlasgowDocumentation


regards
Kai-Uwe Behrmann
                                + development for color
management 
                                + imaging / panoramas
                                + email: ku.bgmx.de
                                + http://www.behrmann.name


Am 19.07.06, 17:46 -0500 schrieb Chris McKinley:

> Kai,
> 
> I see the pmk tar file, and have built it, but there
isn't a pmk file
> available.  I would be happy to start by working on
getting it building under
> whatever build system, but I don't know what the
dependencies are, or what
> needs to be built.  I can probably figure some of this
out, but it would
> take a lot less time to get this going if there were a
list of what the
> requirements are and what in general each subdirectory
produces.  Can you help
> me get this information?
> 
> Thanks,
> 
> -- 
> -Chris McKinley
> 
> On Thu, Jul 20, 2006 at 12:35:43AM +0200, Kai-Uwe
Behrmann wrote:
> > Chris,
> > 
> > Welcome on this mailing list.
> > Thanks for your great offer.
> > 
> > Tom Huffmann prepared something for inclusion into
the Glasgow tree. It is 
> > about the PMK build package. See:
> > http://so
urceforge.net/tracker/index.php?func=detail&aid=1295964&
amp;group_id=75029&atid=542708
> > 
> > PMK was been in the talk because of its simplisity
in contrast to 
> > autotools. To find a maintainer for autotools was
rather hard.
> > 
> > 
> > Nethertheless, if you like autotools and are
familiar with, you are 
> > welcome to use it.
> > 
> > 
> > kind regards
> > Kai-Uwe Behrmann
> >                                 + development for
color management 
> >                                 + imaging /
panoramas
> >                                 + email: ku.bgmx.de
> >                                 + http://www.behrmann.name
> > 
> > 
> > Am 17.07.06, 15:23 -0500 schrieb Chris McKinley:
> > 
> > > Hi,
> > > 
> > > I am a programmer and amateur photographer
who is interested in helping with
> > > Glasgow development on Linux.  I have been a
professional software developer
> > > for about 7 years with a variety of
languages, including C++.  My first goal is
> > > to get a working Glasgow build, but I can't
find any working Makefiles,
> > > automake / autoconf files, or instructions on
where to start.  Can anyone help?
> > > After that, I would like to start with bug
fixes to get my feet wet.
> > > 
> > > -- 
> > > -Chris McKinley
> > > 
> > 

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Cinepaint-developers mailing list
Cinepaint-developerslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ci
nepaint-developers

Thanks! I will take a look at that.

-- 
-Chris McKinley

On Thu, Jul 20, 2006 at 07:42:09AM +0200, Kai-Uwe Behrmann
wrote:
> Chris,
> 
> What I have is a older CVS snapshot before the last
great code 
> reorganisation. There you can have a look at the
various file 
> dependencies at time :
> http://www.behrmann.n
ame/index.php?option=com_weblinks&task=view&catid=67
&id=93
> There is no top source dir build. It would be nice to
configure some 
> options on top and then let make walk in the apropriate
directories.
> The glasgow directory holds the autotooled GUI. 
> 
> 
> A pmk file is not available. It would have to be
created from scratch.
> 
> Dont miss:
> http://cinepaint.bigasterisk.com/GlasgowDocumentation
> 
> 
> regards
> Kai-Uwe Behrmann
>                                 + development for color
management 
>                                 + imaging / panoramas
>                                 + email: ku.bgmx.de
>                                 + http://www.behrmann.name
> 
> 
> Am 19.07.06, 17:46 -0500 schrieb Chris McKinley:
> 
> > Kai,
> > 
> > I see the pmk tar file, and have built it, but
there isn't a pmk file
> > available.  I would be happy to start by working
on getting it building under
> > whatever build system, but I don't know what the
dependencies are, or what
> > needs to be built.  I can probably figure some of
this out, but it would
> > take a lot less time to get this going if there
were a list of what the
> > requirements are and what in general each
subdirectory produces.  Can you help
> > me get this information?
> > 
> > Thanks,
> > 
> > -- 
> > -Chris McKinley
> > 
> > On Thu, Jul 20, 2006 at 12:35:43AM +0200, Kai-Uwe
Behrmann wrote:
> > > Chris,
> > > 
> > > Welcome on this mailing list.
> > > Thanks for your great offer.
> > > 
> > > Tom Huffmann prepared something for inclusion
into the Glasgow tree. It is 
> > > about the PMK build package. See:
> > > http://so
urceforge.net/tracker/index.php?func=detail&aid=1295964&
amp;group_id=75029&atid=542708
> > > 
> > > PMK was been in the talk because of its
simplisity in contrast to 
> > > autotools. To find a maintainer for autotools
was rather hard.
> > > 
> > > 
> > > Nethertheless, if you like autotools and are
familiar with, you are 
> > > welcome to use it.
> > > 
> > > 
> > > kind regards
> > > Kai-Uwe Behrmann
> > >                                 + development
for color management 
> > >                                 + imaging /
panoramas
> > >                                 + email:
ku.bgmx.de
> > >                                 + http://www.behrmann.name
> > > 
> > > 
> > > Am 17.07.06, 15:23 -0500 schrieb Chris
McKinley:
> > > 
> > > > Hi,
> > > > 
> > > > I am a programmer and amateur
photographer who is interested in helping with
> > > > Glasgow development on Linux.  I have
been a professional software developer
> > > > for about 7 years with a variety of
languages, including C++.  My first goal is
> > > > to get a working Glasgow build, but I
can't find any working Makefiles,
> > > > automake / autoconf files, or
instructions on where to start.  Can anyone help?
> > > > After that, I would like to start with
bug fixes to get my feet wet.
> > > > 
> > > > -- 
> > > > -Chris McKinley
> > > > 
> > > 
> 
>
------------------------------------------------------------
-------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get
the chance to share your
> opinions on IT & business topics through brief
surveys -- and earn cash
> http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Cinepaint-developers mailing list
> Cinepaint-developerslists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ci
nepaint-developers
> 


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Cinepaint-developers mailing list
Cinepaint-developerslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ci
nepaint-developers

Chris,

> Thanks! I will take a look at that [the old autotools
files].

Hold on! That's not going to help. The reason I
re-organized the code is 
that it was chaos before. The old directories bore no
obvious 
relationship to the output files produced.

 > I can probably figure some of this out, but it would
 > take a lot less time to get this going if there were a
list
 > of what the requirements are and what in general each
 > subdirectory produces.

Each subdirectory produces one target file: a static lib or
a dso. It 
will be a static lib unless it's a plug-in directory in
which case it's 
a dso or dll. Simple.

The CinePaint Glasgow executable needs to link with every
static lib 
produced plus FLTK, fltable, and pthread. The plug-ins link
with the 
obvious third-party libs (e.g., libjpeg for the JPEG
plug-in).

You can look at the working VC++ project files for guidance.
Those are 
text and not hard to understand.

Robin
--
CinePaint.org





------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Cinepaint-developers mailing list
Cinepaint-developerslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ci
nepaint-developers

OK, that makes sense.  I suspected that each directory's
product was a library
except for the main app, and kind of started in that
direction first.  The VC++
project files look like they do have enough information to
get started.

Which of the other cinepaint-project subdirectories are
used?  I would guess
that I don't need libunistd or libpthread since I am
building this on Linux,
but do I need to get img_img or OpenEXR building first?

Thanks,

-- 
-Chris McKinley


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Cinepaint-developers mailing list
Cinepaint-developerslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ci
nepaint-developers

Chris,

> Which of the other cinepaint-project subdirectories are
used?  I would guess
> that I don't need libunistd or libpthread since I am
building this on Linux,
> but do I need to get img_img or OpenEXR building first?

There's no OpenEXR plug-in for Glasgow yet, only JPEG and
TIFF.

Glasgow is a suite of tools. The glasgow directory contains
the code for 
the cinepaint tool that replaces CinePaint Film Gimp. Other
directories 
contain other tools such as img_img that is a command-line
program sort 
of like ImageMagick convert. Others are CineCalc the
calculator, Mickey 
the hex editor, Splat the simple paint program, and Yage the
gradient 
editor. Planned but not in our CVS yet are a 3D modeler, a
photo 
browser, a movie player, a scanner tool, a monitor
calibration tool, a 
clock sync tool, an HDR viewer, a DV editor, sound tools,
etc.

http://cinep
aint.org/tutorial/index.html

My suggestion is to build the glasgow executable first.
That's the most 
complicated build. The glasgow plug-ins build separately.

Robin
--
CinePaint.org



------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Cinepaint-developers mailing list
Cinepaint-developerslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ci
nepaint-developers