That's fine with me. I went with a top level cmake directory as this is the
convention I found in at least one other project, but if the feeling is that it
is clutter, then I'm happy for it to be moved beneath anetc. I'm new to cmake
and would appreciate any feedback on the new work.
Keith.
+1
-K
- Original Message -
> If nobody minds, I'd like to move the "cmake" directory from the root
> of
> the Proton repository to a new "etc" directory. This directory can be
> used to collect any other build-related and similar files together.
>
> If nobody objects, I'll do that by COB
If nobody minds, I'd like to move the "cmake" directory from the root of
the Proton repository to a new "etc" directory. This directory can be
used to collect any other build-related and similar files together.
If nobody objects, I'll do that by COB today (the 1st).
--
Darryl L. Pierce, Sr. Soft
Strictly speaking it doesn't matter where your build directory is, you just
need to point to the top level cmake rather than the one under proton-c.
--Rafael
On Fri, Feb 1, 2013 at 10:21 AM, Ken Giusti wrote:
> Looks good. I've just pulled a clean version of lastest trunk. I was
> able to bui
On Thu, Jan 31, 2013 at 9:41 AM, Ken Giusti wrote:
> Hi Folks,
>
> I'd like to solicit some ideas regarding $SUBJECT.
>
> I'm thinking we could take an approach similar to what is done on the C++
> broker tests now. That is we should develop a set of "native" send and
> receive programs that can
The package review went very quickly, and the bindings are now up.
Please install them, test them and then give us some karma.
F17:
https://admin.fedoraproject.org/updates/perl-qpid_proton-0.3-2.fc17
F18:
https://admin.fedoraproject.org/updates/perl-qpid_proton-0.3-2.fc18
--
Darryl L. Pierce, Sr
Looks good. I've just pulled a clean version of lastest trunk. I was able to
build and run all tests (proton-j, -c, -jini) on my Fedora 17 box just fine.
One note to proton-c oriented folks: read the top level README file. You need
to mkdir the 'build' directory at the top level rather than
I've got a amqp benchmarking project started at:
https://github.com/chirino/amqp-benchmark
It measures sender/consumer throughput under a bunch of different usage
scenarios. Let me know what your think. We could bring it into the qpid
project if it would make it easier to collaborate on it here.
Keith and I have just merged the jni-binding branch to trunk. We've tested
our changes using the Python test suite and by running the release.sh
script. Nevertheless, this is quite a big commit so some perturbation of
your work is possible.
Let us know if you have any questions.
For your conven
[
https://issues.apache.org/jira/browse/PROTON-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved PROTON-205.
---
Resolution: Fixed
Fixed by http://svn.apache.org/viewvc?rev=1441383&view=rev
> java
[
https://issues.apache.org/jira/browse/PROTON-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Harvey reassigned PROTON-210:
Assignee: Rafael H. Schloming (was: Philip Harvey)
This has been committed to branch
http
[
https://issues.apache.org/jira/browse/PROTON-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Harvey reassigned PROTON-210:
Assignee: Philip Harvey (was: Keith Wall)
> Proton release.sh should create a single r
12 matches
Mail list logo
