Hi Hannah, Thanks for the help, I think I may have found the issue. I opened a craft terminal by using a script that I had created awhile back. Apparently in that script, I had put:
"cd ~/Astroroot/craft-root/ ; source ~/Astroroot/craft-root/craft/craftenv.sh;” Not "cd ~/AstroRoot/craft-root/ ; source ~/AstroRoot/craft-root/craft/craftenv.sh;” So that meant that when craft opened, it got AstroRoot to have the wrong case. It apparently didn’t affect too much, but it did affect the packager. I don’t think it was a mistake, I think I changed the directory name because I liked it better. I just never changed the craft launching script to match it. Thanks, Rob > On Apr 20, 2020, at 9:30 AM, Hannah von Reth <vonr...@kde.org> wrote: > > Craftmaster might use a manually set Root, can you check the spelling in your > config? > > > Cheers, > > Hannah > > On 20.04.20 14:06, Robert Lancaster wrote: >> Hi Hannah, >> >> So I am using some of my own recipes, but yes I am using craft master. I >> just did a complete rebuild about 2 days ago, deleting the whole directory >> so it’s a fresh craft version. And it’s probably nothing to do with the >> recipes because it’s the craft function craftRoot that is returning a >> different path than it actually is in on the computer. >> >> Thanks, >> >> Rob >> >>> On Apr 20, 2020, at 4:48 AM, Hannah von Reth <vonr...@kde.org> wrote: >>> >>> Hi Robert, >>> >>> I have not the slightest idea what could cause this. >>> >>> There aren't any sym links involved in your root, are there? >>> >>> Are you using craftmaster or is it a manual setup? >>> >>> >>> Cheers, >>> >>> Hannah >>> >>>> On 20.04.20 00:42, Robert Lancaster wrote: >>>> Hey guys, >>>> >>>> I thought I would try the craft package utility to see if it is working >>>> well now. I usually package up KStars using my own script, but I thought >>>> it might be worth a try to see how it has progressed. I ran into a very >>>> interesting issue. My craft root directory is >>>> "/Users/rlancaste/AstroRoot/craft-root” but craft thinks it is >>>> "/Users/rlancaste/Astroroot/craft-root”. Note the case issue with >>>> AstroRoot. I don’t know why craft got this information wrong, but it >>>> doesn’t generally cause any issue because the Mac is not case-sensitive. >>>> That was until I tried the packager. The problem I encounter is that some >>>> of my dylib’s have an ID that corresponds to the actual path on the >>>> computer, for example: >>>> "/Users/rlancaste/AstroRoot/craft-root/lib/libgsl.23.dylib,” but when I >>>> try to run the package utility, it does a case-sensitive check to see if >>>> this library is in the craft-root directory. It IS in the craft root >>>> directory, and works just fine, but the packager doesn’t think it is >>>> because its ID doesn’t match what it thinks is the craft root directory. >>>> So as a result, I get errors that look like this: "reference to absolute >>>> library path outside craftroot” even though it is actually in the craft >>>> root directory. So to fix this, craft would either need to get my root >>>> directory path with the correct case, or it would need to do the packager >>>> check to see if it is in the root directory in a non case sensitive way. >>>> >>>> Thanks, >>>> >>>> Rob Lancaster >
