[jira] [Updated] (PROTON-272) Run tests on an installed system.
[ https://issues.apache.org/jira/browse/PROTON-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-272: --- Priority: Minor (was: Major) > Run tests on an installed system. > - > > Key: PROTON-272 > URL: https://issues.apache.org/jira/browse/PROTON-272 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Minor > > Reduce duplication of paths etc. between config.sh and CMakeList.txt. Provide > a way to run the tests on an installed system. > The config.sh in the proton root directory does all the environmental > configuration necessary for each of the bindings to find appropriate modules, > etc. It's really handy for when you want to run code/examples on the command > line out of a source tree build rather than having to install everything. I > believe much of that logic is duplicated here. I know the config.sh isn't > exactly cross-platform, but is there a way to eliminate or reduce some of the > duplication? > A related question is how to run these tests off of an installed system. > Right now the tests appear to pass, however if you actually try and install > the ruby binding and run anything you can't even import the module because > the install is messed up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-272) Run tests on an installed system.
[ https://issues.apache.org/jira/browse/PROTON-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-272: --- Assignee: (was: Alan Conway) > Run tests on an installed system. > - > > Key: PROTON-272 > URL: https://issues.apache.org/jira/browse/PROTON-272 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Reporter: Alan Conway >Priority: Minor > > Reduce duplication of paths etc. between config.sh and CMakeList.txt. Provide > a way to run the tests on an installed system. > The config.sh in the proton root directory does all the environmental > configuration necessary for each of the bindings to find appropriate modules, > etc. It's really handy for when you want to run code/examples on the command > line out of a source tree build rather than having to install everything. I > believe much of that logic is duplicated here. I know the config.sh isn't > exactly cross-platform, but is there a way to eliminate or reduce some of the > duplication? > A related question is how to run these tests off of an installed system. > Right now the tests appear to pass, however if you actually try and install > the ruby binding and run anything you can't even import the module because > the install is messed up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-272) Run tests on an installed system.
[ https://issues.apache.org/jira/browse/PROTON-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-272: --- Summary: Run tests on an installed system. (was: ctest to run python tests on an installed system.) Run tests on an installed system. - Key: PROTON-272 URL: https://issues.apache.org/jira/browse/PROTON-272 Project: Qpid Proton Issue Type: Improvement Components: proton-c Reporter: Alan Conway Assignee: Alan Conway Reduce duplication of paths etc. between config.sh and CMakeList.txt. Provide a way to run the tests on an installed system. The config.sh in the proton root directory does all the environmental configuration necessary for each of the bindings to find appropriate modules, etc. It's really handy for when you want to run code/examples on the command line out of a source tree build rather than having to install everything. I believe much of that logic is duplicated here. I know the config.sh isn't exactly cross-platform, but is there a way to eliminate or reduce some of the duplication? A related question is how to run these tests off of an installed system. Right now the tests appear to pass, however if you actually try and install the ruby binding and run anything you can't even import the module because the install is messed up. -- 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
