Bug 785734

Summary:

Solaris client tarball examples - missing makefile[s]

Product:

Red Hat Enterprise MRG

Reporter:

Frantisek Reznicek <freznice>

Component:

qpid-cpp

Assignee:

Cliff Jansen <cjansen>

Status:

NEW ---

QA Contact:

MRG Quality Engineering <mrgqe-bugs>

Severity:

medium

Docs Contact:

Priority:

medium

Version:

2.1

CC:

iboverma, jross

Target Milestone:

---

Target Release:

---

Hardware:

sparc64

OS:

Solaris

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Attachments:

Description	Flags
Example code Makefiles	none

Description Frantisek Reznicek 2012-01-30 13:46:50 UTC

Description of problem:

Solaris client tarball contains example clients, but no makefile or  CMakeLists.txt.


Version-Release number of selected component (if applicable):
qpid-soleap0.tar.gz (2011-12-13)

How reproducible:
100%

Steps to Reproduce:
1. tar xzf qpid-soleap0.tar.gz | grep -iE '(makefile|CMakeLists.txt)'
  
Actual results:
No makefile[s].

Expected results:
Makefile and/or CMakeLists.txt present



Additional info:

Comment 1 Frantisek Reznicek 2012-01-30 15:10:20 UTC

Created attachment 558357 [details]
Example code Makefiles

Attached makefiles were created during testing c++ solaris client and use QPID_HOME env. variable for directory where is the client code extracted.

Comment 2 Justin Ross 2012-11-06 19:31:01 UTC

Cliff, what's the status of this one?

Comment 3 Cliff Jansen 2012-11-06 22:34:28 UTC

I have not looked at this yet.

There remain several days of CMake "wrestling" to get a clean push-button build (RPATH interaction with Solaris CC args).  I was deferring that and looking at this bz in case feedback from early adopters indicated either or both needed major tweaking.

The attachment is presumably gcc based (as was the tarball) and would need to be extended (or CMake'd) to also work with the native compiler.