Help/Support Makefile EXTRA_FRAMEWORKS not working properly

Ted2 · August 8, 2020

Hellow,

I'm having a weird problem, at least it seems weird to me.
So I've created a framework with the theos framework NIC template.

Then I added it to my project makefile like:

<PROJECT>_EXTRA_FRAMEWORKS += MyFramework
  
This didn't work, so I also tried
  
<PROJECT>_EXTRA_FRAMEWORKS += MyFramework
  
Also not working

Then I install this deb, and it's stating it can't find the framework (which is true, because it's not being installed on device).

If I install the .deb from the framework template, it does work (because then it installs).

Is there a way to not needing to install the framework .deb manually?

Cheers

bR34Kr · August 8, 2020

Where does it install the framework and what says that it cannot find it?

Ted2 · August 8, 2020

17 minutes ago, bR34Kr said:

Where does it install the framework and what says that it cannot find it?

Well, I don't see it in the logs but I assumed it because of: https://github.com/theos/theos/issues/110#issuecomment-399726407

I set framework install_path to System/Libary/Frameworks, which when I install the framework .deb it does install it there.

If I remove framework .deb, & just install the tweak, it doesn't.

I see the /System/Libary/Frameworks/Framework name in the tweaks.dylib, that's why I assumed it couldn't find it.

bR34Kr · August 8, 2020

4 minutes ago, Ted2 said:

Well, I don't see it in the logs but I assumed it because of: https://github.com/theos/theos/issues/110#issuecomment-399726407

I set framework install_path to System/Libary/Frameworks, which when I install the framework .deb it does install it there.

If I remove framework .deb, & just install the tweak, it doesn't.

I see the /System/Libary/Frameworks/Framework name in the tweaks.dylib, that's why I assumed it couldn't find it.

So you want the Framework to only be on the compiler’s device?

If so install your framework to $THEOS/lib and add its headers to $THEOS/include

Ted2 · August 8, 2020

1 minute ago, bR34Kr said:

So you want the Framework to only be on the compiler’s device?

If so install your framework to $THEOS/lib and add its headers to $THEOS/include

No, I want the end user not needing to install the framework manually, but now I'm thinking that's not even a thing lol

bR34Kr · August 8, 2020

Just now, Ted2 said:

No, I want the end user not needing to install the framework manually, but now I'm thinking that's not even a thing lol

Yeah it’s possible. Try installing it to the Theos path. Maybe it’s detecting it resides in the System files so it assumes it’s universal and dynamically links

Ted2 · August 8, 2020

Just now, bR34Kr said:

Yeah it’s possible. Try installing it to the Theos path. Maybe it’s detecting it resides in the System files so it assumes it’s universal and dynamically links

The framework template automatically sets the framework to $THEOS/lib (so it's already there).
INSTALL_PATH is a makefile setting, for where the framework is installed when it's being installed.

I don't think I should set INSTALL_PATH to theos/lib, because most end users wouldn't even have theos installed, right?

bR34Kr · August 8, 2020

4 minutes ago, Ted2 said:

The framework template automatically sets the framework to $THEOS/lib (so it's already there).
INSTALL_PATH is a makefile setting, for where the framework is installed when it's being installed.

I don't think I should set INSTALL_PATH to theos/lib, because most end users wouldn't even have theos installed, right?

Why do you need INSTALL_PATH though?