-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building/testing modifies source tree #1364
Comments
install.py is generated by CMake (look for instally.py.in) and can pretty much be moved anywhere, but it probably look for the directory Packages and ocntrib (and maybe install) straight under itself. This whole CDAT install.py file really needs to be taken out completely and we should create a simple [package/contrib]_pkg.cmake etc.. for each pure CDAT packages (or replace dat_pkg). Since everything under there is now pure PYthon (I took libcdms2 out of it if I remember correctly). The junk file is probably useless. Not sure about Tom's bit. @dlonie why don't you re-apply @ThomasMaxwell baseline issue fix you had and we will say that is issue is about taking out install.py all together. |
We'll look into it, but first I'd like know why @ThomasMaxwell changed it -- I don't want to revert someone else's work without understanding why they made their changes, in case doing so would introduce a problem. |
The revert must have been a merge artifact. I’m not aware of any changes of this sort. — Tom From: David Lonie <notifications@github.commailto:notifications@github.com> We'll look into it, but first I'd like know why @ThomasMaxwellhttps://github.com/ThomasMaxwell changed it -- I don't want to revert someone else's work without understanding why they made their changes, in case doing so would introduce a problem. — |
Ok, thanks -- I'll see about getting that fixed up. |
@sankhesh will take a look at the |
The following files are created in the source tree when building/testing UVCDAT:
I'm not sure what the purpose of the first two are, but the third contains a path to the baseline directory for the
dv3d
tests. I had added a mechanism to properly pass that path intodv3d
via an argument[1], but it appears @ThomasMaxwell reverted my change at some point. This should be cleaned up -- Source clutter with build-dependent info will cause issues when multiple builds reference the same source tree.[1] 65d545a#diff-d3e8161439180f671ad7a70585da5cc3
The text was updated successfully, but these errors were encountered: