qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Qpid > Proton build system proposals
Date Thu, 24 Jan 2013 09:48:01 GMT
    <base href="https://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/2042/9/21/_/styles/combined.css?spaceKey=qpid&amp;forWysiwyg=true"
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="https://cwiki.apache.org/confluence/display/qpid/Proton+build+system+proposals?focusedCommentId=30750132#comment-30750132">Proton
build system proposals</a></h2>
        <b>comment added</b> by              <a href="https://cwiki.apache.org/confluence/display/~godfrer">Rob
    <div class="notificationGreySide">
       <p>If I follow Gordon's second suggestion correctly this would mean we would
have two distinct build systems that you can initiate from the top level of the proton tree.</p>

<p>Then, from the top level directory we could do </p>

<p>mvn package</p>

<p>or mkdir build ; cd build ; cmake .. ; make</p>

<p>to build the Java or C components respectively.  In the second case this would include
the JNI binding.</p>

<p>I'm quite fond of this as a proposal.  To my mind it also makes the preparation of
source tarballs that are strict subsets of the proton source tree easier.  To release a C
source tarball we would simply tar up the proton-c, test and proton-j/proton-api directories
(excluding all the pure java implementation sources).  To produce a Java source tarball we
would tar up the proton-j and test directories.</p>

                <div style="border-bottom: 1px solid #ddd; padding: 10px 20px 7px 20px;">
        <strong>In reply to a comment by <a href="/confluence/display/~gsim@redhat.com"
                          class="url fn confluence-userlink" data-username="gsim@redhat.com"
                   >Gordon Sim</a>:</strong><br/>
        <p>Suggested alternatives (I have not pursued these in detail to see whether
there are issues preventing them being implemented):</p>

	<li>have JNI binding as a distinct component dependent on both the pure java proton
library and the c proton library</li>

	<li>have two parallel build systems - e.g. mvn &amp; cmake/make - that can each
detect the availability of requisite tools (javac, gcc, swig etc) and build only those components
that the available tools enable (windows may be more problematic here since cmake creates
a visual studio project file I believe which may be less flexible than make).</li>

    <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href="https://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>
       <a href="https://cwiki.apache.org/confluence/display/qpid/Proton+build+system+proposals?focusedCommentId=30750132#comment-30750132">View
       <a id="reply-30750132" href="https://cwiki.apache.org/confluence/display/qpid/Proton+build+system+proposals?replyToComment=30750132#comment-30750132">Reply
To This</a>


To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org

View raw message