Ticket #38 (closed defect: invalid)

Opened 1 year ago

Last modified 1 month ago

(249) File system error with non /sdr directory install

Reported by: cdietric Assigned to: shereef
Priority: major Milestone: 0.7.0
Component: ossiecf Version:
Keywords: Cc:

Change History

08/30/07 13:15:51 changed by ttsou

The base directory is hardcoded in LoadableDevice? for /sdr. This prevents the use of other install prefixes.

01/11/08 14:20:06 changed by balister

The hardcoded directory is the GPP device code now.

04/11/08 13:09:13 changed by shereef

  • owner changed from cdietric to shereef.
  • milestone set to 0.6.3.

07/24/08 11:33:43 changed by balister

Ignore my comment. The framework you are using contains the device implementation specific code in the framework.

This design choice should be refactored as the code in the framework is implementations specific. The current code in the framework provides support for executable devices. If you where to try supporting FPGA's or DSP's, this code can not be used.

07/25/08 14:08:53 changed by balister

After receiving a couple of questions about this ticket, I'm wondering why this is scheduled for this release?

It appears that the focus of this release is add the CIREN components and defer fixing bugs until the next release. Since fixing this bug will most likely expose bugs in OWD and ALF, it seems like effort spent here would be better spent fixing bugs that actually impact the OSSIE user experience.

Also, it is entirely possible this bug only exists in the un-supported effort that targeted SCA compliance.

07/25/08 14:36:41 changed by bhilburn

  • status changed from new to closed.
  • resolution set to invalid.

Philip's suggestion that this is not a problem for our code-base is correct.

I just tested and verified that custom installation paths work. Installing in non-/sdr directories is not an issue for our code-base.

To confirm, you can install OSSIE in a non-default installation path by configuring it with: 

$ ./configure prefix=<dir>

Just make sure you update your system's library configuration and tell it where the libraries are.