FunkEngine-Public | Funky cross-platform game engine used by Funktronic Labs
kandi X-RAY | FunkEngine-Public Summary
kandi X-RAY | FunkEngine-Public Summary
FunkEngine-Public is a C library. FunkEngine-Public has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.
Funky cross-platform game engine used by Funktronic Labs
Funky cross-platform game engine used by Funktronic Labs
Support
Quality
Security
License
Reuse
Support
FunkEngine-Public has a low active ecosystem.
It has 22 star(s) with 4 fork(s). There are 5 watchers for this library.
It had no major release in the last 6 months.
FunkEngine-Public has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of FunkEngine-Public is current.
Quality
FunkEngine-Public has no bugs reported.
Security
FunkEngine-Public has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
FunkEngine-Public does not have a standard license declared.
Check the repository for any license declaration and review the terms closely.
Without a license, all rights are reserved, and you cannot use the library in your applications.
Reuse
FunkEngine-Public releases are not available. You will need to build from source code and install.
Installation instructions are available. Examples and code snippets are not available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of FunkEngine-Public
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of FunkEngine-Public
FunkEngine-Public Key Features
No Key Features are available at this moment for FunkEngine-Public.
FunkEngine-Public Examples and Code Snippets
No Code Snippets are available at this moment for FunkEngine-Public.
Community Discussions
No Community Discussions are available at this moment for FunkEngine-Public.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install FunkEngine-Public
FunkEngine should build right out of the box, but if it doesn’t work when you run it the first time in Visual Studio, you need to set just a few User Settings. Right click on the Project "FunkEngine" →Properties → Configuration Properties → Debugging.
Working Directory: $(ProjectDir)../../../../../resources
Environment: PATH=$(ProjectDir)../../../../../resources
Command arguments (Optional): -w 1280 -h 720 --windowed
Open File "FunkEngine\code\cpp\engine\config\UserConfig.h"
define "CONFIG_USER" and "CONFIG_USER_GM" (ex. EDDIE)
Framework/Dynamic Libraries - When adding or upgrading a new Framework, you need to hack the Install Directory to point to the relative path to allow shipping with the bundle..
In the directory containing the *.framework file, call: /Applications/Xcode.app/Contents/Developer/usr/bin/install_name_tool -id @executable_path/../Frameworks/Ogg.framework/Ogg Ogg.framework/Ogg
This will point the framework to the relative loocation of the package bundle
Somtimes, you need to handle cross-framework (Vorbis to orbis) references.. you do this: /Applications/Xcode.app/Contents/Developer/usr/bin/install_name_tool -change /Library/Frameworks/Ogg.framework/Versions/A/Ogg @executable_path/../Frameworks/Ogg.framework/Ogg Vorbis.framework/Vorbis
sometimes, you have to manually change directory references for dylib files: /Applications/Xcode.app/Contents/Developer/usr/bin/install_name_tool -id @executable_path/../Frameworks/libLeap.dylib libLeap.dylib
Working Directory: $(ProjectDir)../../../../../resources
Environment: PATH=$(ProjectDir)../../../../../resources
Command arguments (Optional): -w 1280 -h 720 --windowed
Open File "FunkEngine\code\cpp\engine\config\UserConfig.h"
define "CONFIG_USER" and "CONFIG_USER_GM" (ex. EDDIE)
Framework/Dynamic Libraries - When adding or upgrading a new Framework, you need to hack the Install Directory to point to the relative path to allow shipping with the bundle..
In the directory containing the *.framework file, call: /Applications/Xcode.app/Contents/Developer/usr/bin/install_name_tool -id @executable_path/../Frameworks/Ogg.framework/Ogg Ogg.framework/Ogg
This will point the framework to the relative loocation of the package bundle
Somtimes, you need to handle cross-framework (Vorbis to orbis) references.. you do this: /Applications/Xcode.app/Contents/Developer/usr/bin/install_name_tool -change /Library/Frameworks/Ogg.framework/Versions/A/Ogg @executable_path/../Frameworks/Ogg.framework/Ogg Vorbis.framework/Vorbis
sometimes, you have to manually change directory references for dylib files: /Applications/Xcode.app/Contents/Developer/usr/bin/install_name_tool -id @executable_path/../Frameworks/libLeap.dylib libLeap.dylib
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page