ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Sapego (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2823) CPP: Split libcommon in two libraries to get rid of libjvm dependency.
Date Wed, 23 Mar 2016 11:02:25 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208232#comment-15208232
] 

Igor Sapego commented on IGNITE-2823:
-------------------------------------

Vladimir,

Classes that have been moved from binary to core are IgniteEnvironment, BinaryTypeUpdaterImpl
and InteropExternalMemory. They all depend on the JNI.

1. I agree with your concerns about naming. I personally would prefer libjni - libcommon naming
too but there is external dependencies on libcommon that I didn't want to break. As far as
I know at least C# uses libcommon and it would need to use libjni if we are going to change
naming in that way. If it is not a problem I would be happy to change names as suggested.
2. Guid, Timestamp and Date types are currently contained by the libbinary. Do you think it
would be more consistent to move them to libcommon?

> CPP: Split libcommon in two libraries to get rid of libjvm dependency.
> ----------------------------------------------------------------------
>
>                 Key: IGNITE-2823
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2823
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: odbc, platforms
>    Affects Versions: 1.5.0.final
>            Reporter: Igor Sapego
>            Assignee: Igor Sapego
>             Fix For: 1.6
>
>
> Currently libcommon depends on the libjvm but provides other utilities and macros which
other libraries depend upon. So we need to link libcommon always when we use utils even if
we don't use libjvm (e.g. in ODBC driver).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message