Closed MarkRivers closed 3 years ago
This was more or less on purpose to be backward compatible to the time when Stream did not have its own top. If it finds ../configure, it uses that one and installs there. Itherwise it uses its own configure and installs into its own dir.
This was more or less on purpose to be backward compatible to the time when Stream did not have its own top. If it finds ../configure, it uses that one and installs there. Itherwise it uses its own configure and installs into its own dir.
Many sites put stream under the top-level synApps directory, which does have a configure. stream is the only synApps module which installs into $(TOP)/../
I would like to change stream to behave like the other modules, so I don't have those directories in $(TOP)/../ that contain only stream files. What is causing it to behave differently from other synApps modules like asyn? I could not find anything in stream/configure that was doing that. How do I disable this behavior?
Should be solved now in 2.8.16.
This problem is described in this tech-talk thread: https://epics.anl.gov/tech-talk/2020/msg01372.php
I am running stream 2.8.14. I am having a problem that when I build it, the files get installed into $(TOP)/../lib, not into $(TOP)/lib.
This is the git diff of my files and the ones in 2.8.14. I have only commented out streamApp in the top-level Makefile, and modified configure/RELEASE for new locations.
I do a realclean realuninstall and do an ls in stream/ and in stream/../lib. There are no lib/ directories.
I then do the build. After the build there is no stream/lib directory, but there is a stream/../lib/linux-x86_64 directory containing the stream libraries.
If I search for INSTALL_LOCATION in stream/configure I don’t see the problem.
Am I doing something wrong, or why does the distribution version of stream install into $(TOP)/..?