Personal tools
You are here: Home cmgui Old tracker, do not use this anymore

#695: Shared library field dependency on graphics

issuedata
Classification: Bug
Project: cmgui
OS:
Version:
Categories: compilation
Importance: High
Status: Pending
Assigned to:
Created by: stevens
Created at: 2008-06-04
progress
Deadline: 2008-08-03 12:39
Percent done: 0
contact
Name: Richard Christie
Description:
Transcript
#3: 2008-06-06 09:17 (blackett)
This problem means that zinc and the perl/python bindings cannot be built at the
moment.
It seems to keep it working at the moment, we just have to basically remove this
library
until the dynamic binding for find_element_xi_special is done.
I'm not very comfortable with that though, because
it is much harder to create these separations again once they are gone.

#2: 2008-06-04 12:58 (rchristie)

#1: 2008-06-04 12:57 (rchristie)
categories: "()" -> "['compilation', '']"
OS: "Linux" -> "['']"
version: "Development" -> "['']"
importance: "medium" -> "high"
title: "" -> "Shared library field dependency on graphics"
classification: "Feature" -> "Bug"
description: "" -> "Shared library LIB_FINITE_ELEMENT includes REGION_SRCS which now depend on computed fields. Computed_field_find_xi has a "fast path" using OpenGL, meaning the above library would need to include all of regions, fields, finite_element and graphics to be work, which is too much. So we need to at least remove the static OpenGL dependency, i.e. make the "fast path" functionality discoverable at run time if the right libraries are present. I think we want to have a basic LIB_REGION_FIELDS library - need to decide whether finite_element is part of this or can be separated. "

Contributing to this site

Please add to the wiki any relevant information that you think might be useful to other users of this website. For example, you might like to contribute your experiences, questions and answers.

You are encouraged to contribute to this site regardless of your level of experience. Contributions are welcomed from new and regular visitors.

If you ask a question and receive an answer from a developer you should record it in the wiki. This information is extremely useful and can help other users overcome the same problem.

See how to add and edit pages for more information.

Search
Navigation:
Show issue #