You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2012/01/19 16:49:45 UTC
Re: UIMA C++ SDK Release 2.4.0 - license/notice for additional components
distributed with our binary build
I see in the binary build for windows and linux, built versions of other
project's code, such as xerces, activemq-cpp, apr, and icu.
Sometimes I also see xxx and xxxd versions - what does the d suffix mean? e.g.:
icuuc.lib
icuucd.lib
Sometimes I see "static" in the name, e.g.:
xerces-c_2D.lib
xerces-c_static_2D.lib
I assume this means the library has statically linked in other things from the
Operating System. If we're distributing that, what are the things that got
linked, and what licensing/notices are required for distributing these?
One of these components, activemq-cpp, doesn't have any binary distributions,
where I can find the license/notices that go with that. Does our build of this
this, pull in or include any other components that have their own license/notice
requirements?
-Marshall
On 1/16/2012 2:03 PM, Bhavani Iyer wrote:
> Marshall thanks for the reviewing the packages.
>
> Updated uimacpp 2.4.0 builds are available at
> http://people.apache.org/~bhavani/uimacpp-release-candidates/2.4.0/02/
>
> These contain fixes for the various issues reported by Marshall. The
> Windows and
> Linux source distributions now contain the same set of files.
>
> Please review and report any problems you find.
>
> Thanks,
>
> Bhavani
>
> On Tue, Jan 10, 2012 at 4:14 PM, Marshall Schor<ms...@schor.com> wrote:
>
>> In general, the source-release.zip file is supposed to have these
>> properties:
>>
>> 1) it should be the same (with perhaps some minor exceptions) as the svn
>> tag
>> 2) Checking out the tag and "building" from the tag should give some
>> result;
>> getting the source-release.zip file and "building from that, should give
>> essentially the same result.
>>
>> See http://www.apache.org/dev/release.html#what
>>
>> I'm not sure having a linux-source and a windows-source is the best idea
>> for
>> this. Could we have a source-release that looks more like the svn tag, and
>> serves for both windows and linux targets? Or is there some reason that's
>> not
>> such a good approach? Note that current Apache practice is to name this
>> file
>> ....source-release.zip (and only provide the zip form). This is specified
>> (for
>> maven based builds) in the common apache super-pom.
>>
>> -Marshall
>>
>> On 1/9/2012 11:30 AM, Bhavani Iyer wrote:
>>> Hello,
>>>
>>> I'd like to do a release of UIMA C++ SDK.
>>>
>>> The release will include updates to the ActiveMQ C++ service wrapper,
>>> improvements to the Linux build process and bug fixes.
>>>
>>> The source and binary packages are available here:
>>> http://people.apache.org/~bhavani/uimacpp-release-candidates/2.4.0/01/
>>>
>>> The SVN tag is
>>> https://svn.apache.org/repos/asf/uima/uimacpp/tags/uimacpp-2.4.0-rc1
>>>
>>> The issues fixed are listed RELEASE_NOTES.html in the binary zip/tar
>>> release.
>>>
>>> Please install and test the packages and report any problems you find.
>>>
>>> Thanks,
>>> Bhavani
>>>
Re: UIMA C++ SDK Release 2.4.0 - license/notice for additional
components distributed with our binary build
Posted by Bhavani Iyer <bh...@gmail.com>.
The d sufiix is required for the debug build of uimacpp library on Windows.
The "static" are not required for uimacpp. The buildsdk script should be
modified to not copy those over.
ActiveMQ CPP only has a source distribution found here :
http://activemq.apache.org/cms/activemq-cpp-341-release.html
To build ACTIVEMQ CPP you need to have APR and APR-UTIL. APR-UTIL is used
to support message encryption. APR-UTIL is not required for uimacpp and
therefore not included in the UIMA C++ distribution.
.
Bhavani
On Thu, Jan 19, 2012 at 10:49 AM, Marshall Schor <ms...@schor.com> wrote:
> I see in the binary build for windows and linux, built versions of other
> project's code, such as xerces, activemq-cpp, apr, and icu.
>
> Sometimes I also see xxx and xxxd versions - what does the d suffix mean?
> e.g.:
> icuuc.lib
> icuucd.lib
>
> Sometimes I see "static" in the name, e.g.:
>
> xerces-c_2D.lib
> xerces-c_static_2D.lib
>
> I assume this means the library has statically linked in other things from
> the Operating System. If we're distributing that, what are the things that
> got linked, and what licensing/notices are required for distributing these?
>
> One of these components, activemq-cpp, doesn't have any binary
> distributions, where I can find the license/notices that go with that.
> Does our build of this this, pull in or include any other components that
> have their own license/notice requirements?
>
> -Marshall
>
> On 1/16/2012 2:03 PM, Bhavani Iyer wrote:
>
>> Marshall thanks for the reviewing the packages.
>>
>> Updated uimacpp 2.4.0 builds are available at
>> http://people.apache.org/~**bhavani/uimacpp-release-**
>> candidates/2.4.0/02/<http://people.apache.org/%7Ebhavani/uimacpp-release-candidates/2.4.0/02/>
>>
>> These contain fixes for the various issues reported by Marshall. The
>> Windows and
>> Linux source distributions now contain the same set of files.
>>
>> Please review and report any problems you find.
>>
>> Thanks,
>>
>> Bhavani
>>
>> On Tue, Jan 10, 2012 at 4:14 PM, Marshall Schor<ms...@schor.com> wrote:
>>
>> In general, the source-release.zip file is supposed to have these
>>> properties:
>>>
>>> 1) it should be the same (with perhaps some minor exceptions) as the svn
>>> tag
>>> 2) Checking out the tag and "building" from the tag should give some
>>> result;
>>> getting the source-release.zip file and "building from that, should give
>>> essentially the same result.
>>>
>>> See http://www.apache.org/dev/**release.html#what<http://www.apache.org/dev/release.html#what>
>>>
>>> I'm not sure having a linux-source and a windows-source is the best idea
>>> for
>>> this. Could we have a source-release that looks more like the svn tag,
>>> and
>>> serves for both windows and linux targets? Or is there some reason
>>> that's
>>> not
>>> such a good approach? Note that current Apache practice is to name this
>>> file
>>> ....source-release.zip (and only provide the zip form). This is
>>> specified
>>> (for
>>> maven based builds) in the common apache super-pom.
>>>
>>> -Marshall
>>>
>>> On 1/9/2012 11:30 AM, Bhavani Iyer wrote:
>>>
>>>> Hello,
>>>>
>>>> I'd like to do a release of UIMA C++ SDK.
>>>>
>>>> The release will include updates to the ActiveMQ C++ service wrapper,
>>>> improvements to the Linux build process and bug fixes.
>>>>
>>>> The source and binary packages are available here:
>>>> http://people.apache.org/~**bhavani/uimacpp-release-**
>>>> candidates/2.4.0/01/<http://people.apache.org/%7Ebhavani/uimacpp-release-candidates/2.4.0/01/>
>>>>
>>>> The SVN tag is
>>>> https://svn.apache.org/repos/**asf/uima/uimacpp/tags/uimacpp-**
>>>> 2.4.0-rc1<https://svn.apache.org/repos/asf/uima/uimacpp/tags/uimacpp-2.4.0-rc1>
>>>>
>>>> The issues fixed are listed RELEASE_NOTES.html in the binary zip/tar
>>>> release.
>>>>
>>>> Please install and test the packages and report any problems you find.
>>>>
>>>> Thanks,
>>>> Bhavani
>>>>
>>>>