Hi Paul,

On 17 May 2018 at 15:30, Flores, Paul A. <paul.a.flo...@saic.com> wrote:

> UBUNTU uses uuidgen rather then uuid_generate.  This causes issues with
> src/CMakeList.txt "block" from lines 296 thru 320.

If I'm not mistaken, uuidgen is the command-line tool while uuid_generate
is the name of the library function (wrapped by uuidgen) which the cmake
script is looking for in the section you reference.
Can you be more specific about what issues you're seeing? Reporting error
messages would be helpful. It would also be instructive to know what
version of Ubuntu you're using and whether or not you have the "uuid-dev"
package installed as the latter affects the execution path of the script.
Since I've been using Qpid on Ubuntu for several years and haven't had any
issues in this area, I wonder if there might be something unusual about
your environment; perhaps if for example you've installed something
(possibly uuid-related) from source that's affecting things or your build
environment has otherwise become inconsistent (broken apt packages etc)?
Build logs might be informative on this point.

> Immediate resolution is straightforward, alter the script to refer to
> uuidgen (search and replace).
> I would like to suggest a long term resolution is to rely on
> IdentifyOS.cmake  to record the OS into a variable and use accordingly.
> Overall scope of such a change is beyond my understanding of the existing
> cmake structure/organization.

The section of CMake script you mention attempts (correctly, I think) to
discover the relevant interface in an OS-agnostic manner, relying instead
on the libraries and headers it is actually able to locate. Given that even
with knowledge of the precise OS variant the available library interfaces
are still not known, I would say this is the correct approach.

> ________________________________
> This communication (including any attachments) may contain information
> that is proprietary, confidential or exempt from disclosure. If you are not
> the intended recipient, please note that further dissemination,
> distribution, use or copying of this communication is strictly prohibited.
> Anyone who received this message in error should notify the sender
> immediately by telephone or by return email and delete it from his or her
> computer.

Reply via email to