[jira] [Created] (PROTON-406) Cmake build fails to find Ruby vendor location on some platforms
Darryl L. Pierce created PROTON-406: --- Summary: Cmake build fails to find Ruby vendor location on some platforms Key: PROTON-406 URL: https://issues.apache.org/jira/browse/PROTON-406 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.5 Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Priority: Critical Some versions of Cmake fail to provide the needed variables, such as RUBY_VENDORLIB_DIR. In those cases, the Cmake file for Ruby needs to determine the path itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PROTON-405) [proton-c] Windows install fails to find proton-api.jar file
[ https://issues.apache.org/jira/browse/PROTON-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13743839#comment-13743839 ] Chuck Rolke commented on PROTON-405: Code that handles jave==present and bouncycastle==absent is the issue. A system that has no java at all [log1] works much better than one with java but no bouncycastle [log2]. [log1] This built a system that installs OK S:\Users\chug\svn\Proton\buildcmake -DCMAKE_INSTALL_PREFIX=S:/users/chug/svn/proton/install .. -- Building for: Visual Studio 10 -- Check for working C compiler using: Visual Studio 10 -- Check for working C compiler using: Visual Studio 10 -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler using: Visual Studio 10 -- Check for working CXX compiler using: Visual Studio 10 -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- PN_VERSION: 0.5 -- Could NOT find Java (missing: Java_JAR_EXECUTABLE Java_JAVAC_EXECUTABLE Java_JAVAH_EXECUTABLE Java_JAVADOC_EXECUTABLE) -- Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the system variable OPENSSL_ROOT_DIR (missing: OPENSSL_LIBRARIES OPENSSL_INCLUDE_DIR) -- Looking for clock_gettime -- Looking for clock_gettime - not found. -- Looking for clock_gettime in rt -- Looking for clock_gettime in rt - not found -- Looking for GetSystemTimeAsFileTime -- Looking for GetSystemTimeAsFileTime - found -- Looking for uuid_generate -- Looking for uuid_generate - not found. -- Looking for uuid_generate in uuid -- Looking for uuid_generate in uuid - not found -- Looking for uuid_create -- Looking for uuid_create - not found. -- Looking for UuidToString -- Looking for UuidToString - found -- Looking for strerror_s -- Looking for strerror_s - found -- Looking for atoll -- Looking for atoll - not found. -- Looking for _atoi64 -- Looking for _atoi64 - found -- Could NOT find SWIG (missing: SWIG_EXECUTABLE SWIG_DIR) -- Found Doxygen: C:/Program Files (x86)/doxygen/bin/doxygen.exe -- Looking for include files INTTYPES_AVAILABLE -- Looking for include files INTTYPES_AVAILABLE - not found. -- Can't locate the valgrind command; no run-time error detection -- Cannot find rspec, skipping rspec tests -- Cannot find both Java and Maven: testing disabled for Proton-J and JNI Bindings -- Configuring done -- Generating done -- Build files have been written to: S:/Users/chug/svn/Proton/build [log2] This is the system that produces the original issue. D:\Users\crolke\svn\proton\buildcmake -DCMAKE_INSTALL_PREFIX=d:/users/crolke/svn/proton/install .. -- Building for: Visual Studio 10 -- Check for working C compiler using: Visual Studio 10 -- Check for working C compiler using: Visual Studio 10 -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler using: Visual Studio 10 -- Check for working CXX compiler using: Visual Studio 10 -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- PN_VERSION: 0.5 -- Found Java: C:/Program Files/Java/jdk1.6.0_21/bin/java.exe -- Java version: 1.6.0.21. javac is at: C:/Program Files/Java/jdk1.6.0_21/bin/javac.exe Loading Proton's UseJava module -- Locations of Bouncycastle 1.47 jars: BOUNCYCASTLE_BCPROV_JAR-NOTFOUND BOUNCYCASTLE_BCPKIX_JAR-NOTFOUND -- Won't build proton-j-impl because one or more Bouncycastle jars were not found. PROTON_JAR_DEPEND_DIR was: /usr/share/java -- Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the system variable OPENSSL_ROOT_DIR (missing: OPENSSL_LIBRARIES OPENSSL_INCLUDE_DIR) -- Looking for clock_gettime -- Looking for clock_gettime - not found. -- Looking for clock_gettime in rt -- Looking for clock_gettime in rt - not found -- Looking for GetSystemTimeAsFileTime -- Looking for GetSystemTimeAsFileTime - found -- Looking for uuid_generate -- Looking for uuid_generate - not found. -- Looking for uuid_generate in uuid -- Looking for uuid_generate in uuid - not found -- Looking for uuid_create -- Looking for uuid_create - not found. -- Looking for UuidToString -- Looking for UuidToString - found -- Looking for strerror_s -- Looking for strerror_s - found -- Looking for atoll -- Looking for atoll - not found. -- Looking for _atoi64 -- Looking for _atoi64 - found -- Could NOT find SWIG (missing: SWIG_EXECUTABLE SWIG_DIR) -- Found Doxygen: C:/Program Files (x86)/doxygen/bin/doxygen.exe -- Looking for include files INTTYPES_AVAILABLE -- Looking for include files INTTYPES_AVAILABLE - not found. -- Can't locate the valgrind command; no run-time error detection -- Cannot find rspec, skipping rspec tests -- Cannot find both Java and Maven: testing disabled for Proton-J and JNI Bindings -- Configuring done -- Generating done -- Build files have been written to: D:/Users/crolke/svn/proton/build [proton-c] Windows
[jira] [Created] (PROTON-407) [proton-c] Windows install does not install .lib nor .pdb files
Chuck Rolke created PROTON-407: -- Summary: [proton-c] Windows install does not install .lib nor .pdb files Key: PROTON-407 URL: https://issues.apache.org/jira/browse/PROTON-407 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Environment: Windows Reporter: Chuck Rolke In current trunk building the INSTALL project in VS2010 does not place the qpid-proton.lib, qpid-proton.pdb files into the install area. Consequently consumers using an installed kit are unable to link to the qpid-proton library. In a dev environment the files are available in the build area as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (PROTON-408) [proton-c] Windows build does not put d suffix on debug file names
Chuck Rolke created PROTON-408: -- Summary: [proton-c] Windows build does not put d suffix on debug file names Key: PROTON-408 URL: https://issues.apache.org/jira/browse/PROTON-408 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Environment: Windows Reporter: Chuck Rolke Visual Studio projects by default put a d suffix on debug version file names. This lets you have qpid-proton.dll and qpid-protond.dll in the same directory making the files easier to integrate with user projects. Cmake provides trivially easy support for this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PROTON-343) Add a pluggable Proton logging layer
[ https://issues.apache.org/jira/browse/PROTON-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13743875#comment-13743875 ] ASF subversion and git services commented on PROTON-343: Commit 1515455 from [~philharveyonline] in branch 'proton/trunk' [ https://svn.apache.org/r1515455 ] PROTON-343: Removed proton-logging module and its usages (all of which are functionally insignificant), so that the upcoming Proton 0.5 release does not contain this not-yet-prime-time module. Add a pluggable Proton logging layer Key: PROTON-343 URL: https://issues.apache.org/jira/browse/PROTON-343 Project: Qpid Proton Issue Type: Improvement Components: proton-c, proton-j Reporter: Philip Harvey Assignee: Philip Harvey Attachments: 0001-PROTON-343-sketched-out-the-Java-parts-of-the-propos.patch Applications that use Proton sometimes want Proton to produce logging. Goals * Proton should provide a default logging implementation. * It should be easy for Proton client code to provide custom logging implementation, e.g. one that uses the same third party logging framework as their application code. * Proton should not have a compile-time dependency on a third party logging framework * Proton's log output is considered to be part of its public interface. Therefore, in the spirit of Proton's cross-language consistency goals, this output should be consistent between proton-c and proton-j. * The goals that general-purpose logging frameworks try to meet - performance, ease of use etc - also apply. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PROTON-408) [proton-c] Windows build does not put d suffix on debug file names
[ https://issues.apache.org/jira/browse/PROTON-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744116#comment-13744116 ] ASF subversion and git services commented on PROTON-408: Commit 1515559 from c...@apache.org in branch 'proton/trunk' [ https://svn.apache.org/r1515559 ] PROTON-408: [proton-c] Windows build does not put d suffix on debug file names [proton-c] Windows build does not put d suffix on debug file names Key: PROTON-408 URL: https://issues.apache.org/jira/browse/PROTON-408 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Environment: Windows Reporter: Chuck Rolke Visual Studio projects by default put a d suffix on debug version file names. This lets you have qpid-proton.dll and qpid-protond.dll in the same directory making the files easier to integrate with user projects. Cmake provides trivially easy support for this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (PROTON-408) [proton-c] Windows build does not put d suffix on debug file names
[ https://issues.apache.org/jira/browse/PROTON-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke resolved PROTON-408. Resolution: Fixed Resolved in Commit 1515559 from c...@apache.org in branch 'proton/trunk' [ https://svn.apache.org/r1515559 ] [proton-c] Windows build does not put d suffix on debug file names Key: PROTON-408 URL: https://issues.apache.org/jira/browse/PROTON-408 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Environment: Windows Reporter: Chuck Rolke Visual Studio projects by default put a d suffix on debug version file names. This lets you have qpid-proton.dll and qpid-protond.dll in the same directory making the files easier to integrate with user projects. Cmake provides trivially easy support for this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
