Modify ↓

Opened 14 years ago

Closed 13 years ago

#23 closed enhancement (wontfix)

Detect UFO libraries in neighboring directories

Reported by: Suren A. Chilingaryan Owned by: Matthias Vogelgesang
Priority: minor Milestone:
Component: libuca Version:
Keywords: Cc:

Description

I expect that multiple people will work on the UFO servers in parallel adjusting parts of UFO stack. For this reason relaying only on the libraries installed in the system is not enough. CMake scripts should detect libraries in sibling subfolders. I mean the build set of ufo libraries may be just stored and builded in test folder like this:

->test
  |-- libpf64
  |-- libuca
  |-- libufo

Attachments (2)

cmake_find_pflib.diff​ (1.1 KB) - added by Suren A. Chilingaryan 14 years ago.
Proposed fix to find libpf
cmake_find_pco.diff​ (873 bytes) - added by Suren A. Chilingaryan 14 years ago.

Download all attachments as: .zip

Change History (4)

Changed 14 years ago by Suren A. Chilingaryan

Attachment: cmake_find_pflib.diff​ added

Proposed fix to find libpf

comment:1 Changed 14 years ago by Matthias Vogelgesang

I don't think this is a good idea:

  1. Why rely on directory structures like that? This can change and then we have to change the CMake files again.
  1. If things are fixed and set up, libraries like libpf and libuca won't change too often. And if something changes, it is as easy as typing sudo make install to update. That's why we agree on interfaces rather than particular implementations.
  1. This is a very ad-hoc and non-standard way of building things.

Changed 14 years ago by Suren A. Chilingaryan

Attachment: cmake_find_pco.diff​ added

comment:2 Changed 13 years ago by Matthias Vogelgesang

Resolution: → wontfix
Status: new → closed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Matthias Vogelgesang.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences.

Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.