opened
johnkit
username_0
The main issue is that the installed version of the __init__.py is getting written to the "install/install/libexec/...", that is, there are 2 "install" items in the path when there should be one.

This mod also restores the configure_file command that is applied to the __init__.py file
that is written to the install directory.

Note that this change will affect superbuilds that use SMTK (which are probably already hosed by the extra "install" item in the path).
Fix install logic for smtk/__init__.py
issue
created
johnkit
username_0
After a bit more thought, I think we should merge this commit as is. By removing CMAKE_INSTALL_PREFIX from line 155, the value for SMTK_PYTHON_MODULEDIR will *always* be a relative path, so that the downstream install command will act in a consistent way. Otherwise, developers who user SMTK will have to know that the python module gets installed differently depending on whether they specify CMAKE_INSTALL_PREFIX as a relative or absolute path.

If it helps, we *could* rename SMTK_PYTHON_MODULEDIR to something like SMTK_PYTHON_MODULE_RELATIVE_PATH;  but personally, I think the variable name is long enough already :)
comment
created
vibraphone
username_1
@username_0 I guess I am OK with relative paths there.
comment
created
johnkit
username_0
Can this PR be merged? Our new intern Dylan is building CMB on Ubuntu and hitting the same problem.
comment