Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]
Photo

How to connect an external library base at compilation?
Started by pahuchiy Sep 07 2019 10:26 AM

2 replies to this topic
[TOPIC CONTROLS]
[/TOPIC CONTROLS]
[modOptionsDropdown]
[/modOptionsDropdown]
[reputationFilter]
[TOPIC: post.html]
#1

pahuchiy

[GLOBAL: userInfoPane.html]
pahuchiy
  • Observer

  • 13 posts
  • Corona SDK

how to connect an external library base at compilation?
External libraries are used in several projects and are not in the project folder. How at compilation not to copy them to the project folder?
In the simulator, you can specify any path on the computer, but libraries cannot be found on the device.


[TOPIC: post.html]
#2

XeduR @Spyric

[GLOBAL: userInfoPane.html]
XeduR @Spyric
  • Contributor

  • 989 posts
  • Corona SDK

I don't think that this is possible. You need to include the files you want to use inside the project folder.

 

If you need to manage the same file in different projects from a single location, you could look into Git submodules.



[TOPIC: post.html]
#3

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 26,331 posts
  • Enterprise

Corona offer's two modes to work:

 

1. The simulator. It does all the work for you. From the simulator you can build your app for your destination app or store. In this mode, you can only use the API's that Corona provides or any plugins from the Marketplace. You cannot link to external third-party libraries.

 

2. Corona Native builds. These allow you to use Xcode, Android Studio (or Visual Studio for Windows desktop) to build your Corona app. We include a Lua->C Bridge interface so you can write native code and call it from Lua. It's probably easier to still use our plugin interface to simply this. In this case you can use third-party external libraries.

 

Most Corona users are happy with simulator builds. Using native builds is a bit more advanced. 

 

Rob




[topic_controls]
[/topic_controls]