Sorry about wrong tarball version. Attached again.

-Simon

On Wed, 2008-01-30 at 16:02 +0800, simon.zheng at sun.com wrote:
> Hi All,
> 
> Refering to Laca's comment, updated spec files. Please note it doesn't
> include g++ library for the time being. And this spec file is only
> available for Neveda rather than vermillion-devel since Indiana target
> build SNV_85 still uses stable GNOME 2.20. 
> 
> Ghee, 
> 
> I haven't tried to build stable glibmm on vermillion-devel. Could you
> try with developing glibmm? I guess glibmm change a lot in accordance
> with glib. So we need two spec files, one is for Neveda, another is for
> vermillion-devel. But only the former is what Indiana cares about, the
> latter will upgrade with GNOME 2.22 once glibmm is integrated into
> Neveda/Indiana.
> 
> Thanks,
> -Simon
> 
> On Tue, 2008-01-29 at 11:38 +0000, Ghee Teo wrote:
> > Hi Simon,
> > 
> > When I tried to built SFEglibmm.spec from SFE yesterday on vermillion-devel,
> > I came across some build problem because glib has moved g_assert () from
> > messages.h to gtestutils.h in gnome 2.21.x, how are you handling this?
> > 
> > -Ghee
> > 
> > simon.zheng at sun.com wrote:
> > > Hi,
> > >
> > > Glibmm is a set of C++ bindings for Glib2 Library, including
> > > cross-platform APIs such as a std::string-like UTF8 string class, string
> > > utility methods, such as a text encoding converter API, file access, and
> > > threads.
> > >
> > > Spec files are based on SFE version and changed a little. Please
> > > review. 
> > >
> > > Thanks,
> > > -Simon
> > >   
> > 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SUNWglibmm.spec
Type: text/x-rpm-spec
Size: 3000 bytes
Desc: not available
URL: 
<http://mail.opensolaris.org/pipermail/jds-review/attachments/20080130/9bbd3ea7/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: glibmm.spec
Type: text/x-rpm-spec
Size: 2294 bytes
Desc: not available
URL: 
<http://mail.opensolaris.org/pipermail/jds-review/attachments/20080130/9bbd3ea7/attachment-0001.bin>

Reply via email to