Thanks. It was ambiguous. Looked like it was optional and had a default (which it did)
Now hopefully people can just deduce more info about the examples from the examples/README.txt and PROTON-100 can be ignored ;-) Sent from my iPhone On Oct 25, 2012, at 4:14 AM, Rafael Schloming <[email protected]> wrote: > Done. I stopped short of putting "Hey William! Set the install prefix." ;-) > > --Rafael > > On Wed, Oct 24, 2012 at 11:22 PM, William Henry <[email protected]> wrote: > >> Change: >> # depending on your system you may want to adjust the install prefix >> cmake -DCMAKE_INSTALL_PREFIX=/usr .. >> >> To: >> # Set the install prefix. You may need to adjust depending on your system >> cmake -DCMAKE_INSTALL_PREFIX=/usr .. >> >> >> ----- Original Message ----- >>> It looks like you installed everything into /usr/local. I'm guessing >>> the >>> system python (installed in /usr) does not look under /usr/local as >>> part of >>> it's module search path. Try installing into /usr instead. >>> >>> --Rafael >>> >>> On Wed, Oct 24, 2012 at 10:10 PM, William Henry <[email protected]> >>> wrote: >>> >>>> $ more build/install_manifest.txt >>>> /usr/local/bin/proton >>>> /usr/local/bin/proton-dump >>>> /usr/local/lib64/libqpid-proton.so >>>> /usr/local/include/proton/parser.h >>>> /usr/local/include/proton/util.h >>>> /usr/local/include/proton/ssl.h >>>> /usr/local/include/proton/scanner.h >>>> /usr/local/include/proton/cproton.i >>>> /usr/local/include/proton/messenger.h >>>> /usr/local/include/proton/message.h >>>> /usr/local/include/proton/sasl.h >>>> /usr/local/include/proton/driver.h >>>> /usr/local/include/proton/types.h >>>> /usr/local/include/proton/buffer.h >>>> /usr/local/include/proton/framing.h >>>> /usr/local/include/proton/codec.h >>>> /usr/local/include/proton/engine.h >>>> /usr/local/include/proton/error.h >>>> /usr/local/share/proton/LICENSE >>>> /usr/local/share/proton/README >>>> /usr/local/share/proton/TODO >>>> /usr/local/lib64/pkgconfig/libqpid-proton.pc >>>> /usr/local/lib64/python2.7/site-packages/cproton.py >>>> /usr/local/lib64/python2.7/site-packages/cproton.pyc >>>> /usr/local/lib64/python2.7/site-packages/cproton.pyo >>>> /usr/local/lib64/python2.7/site-packages/proton.py >>>> /usr/local/lib64/python2.7/site-packages/proton.pyc >>>> /usr/local/lib64/python2.7/site-packages/proton.pyo >>>> /usr/local/lib64/python2.7/site-packages/_cproton.so >>>> /usr/local/lib64/ruby/cproton.so >>>> /usr/local/lib64/php/modules/cproton.so >>>> /usr/local/share/php/cproton.php >>>> /usr/local/share/php/proton.php >>>> /etc/php.d/cproton.ini >>>> >>>> >>>> ----- Original Message ----- >>>>> Can you post the contents of your install_manifest.txt? >>>>> >>>>> On Wed, Oct 24, 2012 at 9:50 PM, William Henry >>>>> <[email protected]> >>>>> wrote: >>>>> >>>>>> Ok install was successful. Still have an ImportError for >>>>>> proton. >>>>>> >>>>>> Not sure what I'm missing >>>>>> >>>>>> William >>>>>> >>>>>> Sent from my iPhone >>>>>> >>>>>> On Oct 24, 2012, at 7:29 PM, Rafael Schloming >>>>>> <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> The examples should work without the config.sh, it just sets >>>>>>> up >>>>>>> stuff for >>>>>>> the dev environment. If you do the make install, all the >>>>>>> proton >>>>>>> stuff >>>>>>> should be available without any special environmental config. >>>>>>> >>>>>>> --Rafael >>>>>>> >>>>>>> On Wed, Oct 24, 2012 at 8:11 PM, William Henry >>>>>>> <[email protected]> >>>>>> wrote: >>>>>>> >>>>>>>> Are the examples supposed to work for this release? Because >>>>>>>> the >>>>>>>> instructions don't tell people how to get them running. I >>>>>>>> don't >>>>>>>> see the >>>>>>>> config.sh file. (I mentioned this in a previous email. I'll >>>>>>>> log >>>>>>>> a Jira.) >>>>>>>> >>>>>>>> William >>>>>>>> >>>>>>>> ----- Original Message ----- >>>>>>>>> I've put up an RC3 here: >>>>>>>>> >>>>>>>>> http://people.apache.org/~rhs/qpid-proton-0.1rc3/ >>>>>>>>> >>>>>>>>> The following are the changes from RC2: >>>>>>>>> >>>>>>>>> - added README and LICENSE for proton-j >>>>>>>>> - updated the proton-c README >>>>>>>>> - fixed cmake build to not use the OPTIONAL thing for >>>>>>>>> older >>>>>>>>> versions >>>>>>>>> - fixed detection of LIB_SUFFIX (i.e. we won't install >>>>>>>>> into >>>>>>>>> lib64 >>>>>>>>> on 32 >>>>>>>>> bit systems anymore) >>>>>>>>> >>>>>>>>> --Rafael >>
