To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=81093





------- Additional comments from [EMAIL PROTECTED] Tue Sep 18 11:45:36 +0000 
2007 -------
I'm going to attach a tarball containing the subproject to be added to external.

The tarball contains the new parts to be added to external, expand it somewere:
the patch contained (external-icc.patch, m227 based) can be used to add the new
external/icc to external/prj/build.lst and  external/prj/d.lst, the tar archive
(external-new-icc.tar.gz) contains the new parts to be added to the project
external, it should be expanded in OOo source root.

The icc library and applications are build when the external project is build,
since it's build before vcl, I didn't modify the vcl build dependance. In this
way I don't think that a module alias is needed.

In the end a new file (sRGB-IEC61966-2.1.hxx) will be delivered to solver, to be
then included in the pdfwriter_impl.cxx file in vcl project.

I tried to build it on Windows, on a 2.2.1 build tree I have in place, I had to
modify the external build.lst and d.lst manually ( the  external-icc.patch
didn't worked there) but the library built and the include file was correctly
delivered.
In MAC and Solaris it's to be checked.

@rene: is this structure ok for OOo projects?

@pl: is this ok for vcl inclusion?

As soon as I have some feedback I'll see how to add it to CVS.


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to