• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Vincent_M

Dependencies

6 posts in this topic

My last post didn't save on my phone^

I have a bunch of code that require a few libraries such as cURL and LUA to build. I'd like to make the installation as simple as possible and run on quote a few operating systems. Would it be best just to list the dependencies and have then install it or provide the correct version of each library in the download since they're GNU licensed?
0

Share this post


Link to post
Share on other sites
When distributing code you should provide all libraries, dll's the executable needs to run. These should also exist in the right location usually the install directory of the application, but in the case of C++ runtime on windows you should run the redist installer instead, same goes for Direct X. The latter two are free to redistribute with your application. As for Other Os I have not enough experience with those to comment on this, but it boils down to the similar fact that you should apply all the dependencies it requires, a-la apt-get install fashion for Debian and derivatives for example where it asks the user to install the dependent libraries. Edited by NightCreature83
2

Share this post


Link to post
Share on other sites

I'd like to stay away from having a separate distro per platform at this time since since it's so early on. Another reason is because you're able to develop for multiple platforms per OS. For example, on Mac, you can develop Mac, iOS, Android/OUYA, and possibly PS Vita (assuming it's the full SDK) games. So for this, I'd like to have it to where people can just drop their code where they feel comfortable, and drag and drop files.

 

I definitely agree with NightCreature83's suggestion about providing all libraries. This concerns me with Linux, however, since there are so many different distros of that OS, and it seems commonplace, from my experience, to build the libraries from source using that specific distro's source code repository (generally through apt-get install, etc) so the binaries match up with the OS's 'dialect'. I'm assuming that some distros of Linux have modified kernels, but I'm quite new in this area!

 

Having an install script for Linux was something I think would be a good idea. That's something I'll need to learn how to do when I have free time.

 

One thing I've done in the past, and it's probably bad practice, but if I have to install any development DLLs such as glu32, glew32.dll, etc, I'd just add them into my Windows' system/system32 directory. I understand that could be malicious by sticking foreign DLLs into, but it was a sandbox environment. I'd like to have some way of Visual Studio just to drop the necessary DLLs into the executable's directory for the release build to automate things. It seems easy enough, but that's yet another responsibility my engine would require developers using it. It's a small step developers could overlook --and that goes for me too! lol

0

Share this post


Link to post
Share on other sites

I'd like to stay away from having a separate distro per platform at this time since since it's so early on. Another reason is because you're able to develop for multiple platforms per OS. For example, on Mac, you can develop Mac, iOS, Android/OUYA, and possibly PS Vita (assuming it's the full SDK) games. So for this, I'd like to have it to where people can just drop their code where they feel comfortable, and drag and drop files.

 

I definitely agree with NightCreature83's suggestion about providing all libraries. This concerns me with Linux, however, since there are so many different distros of that OS, and it seems commonplace, from my experience, to build the libraries from source using that specific distro's source code repository (generally through apt-get install, etc) so the binaries match up with the OS's 'dialect'. I'm assuming that some distros of Linux have modified kernels, but I'm quite new in this area!

 

Having an install script for Linux was something I think would be a good idea. That's something I'll need to learn how to do when I have free time.

 

One thing I've done in the past, and it's probably bad practice, but if I have to install any development DLLs such as glu32, glew32.dll, etc, I'd just add them into my Windows' system/system32 directory. I understand that could be malicious by sticking foreign DLLs into, but it was a sandbox environment. I'd like to have some way of Visual Studio just to drop the necessary DLLs into the executable's directory for the release build to automate things. It seems easy enough, but that's yet another responsibility my engine would require developers using it. It's a small step developers could overlook --and that goes for me too! lol

 

apt-get install doesn't do any compiling it only gets and installs *.deb packages for you which are all precompiled.

 

You should never ever copy anything into the system, system32 or SySWOW64 directories in windows, unless it is through an official installer, read up on dll hell. If you really want to distribute your own versions of these dlls, put the next to the executable as the dll loader will look in that directory before any other one. Currently all dependencies are installed in WinSxS (side-by-side installation of dlls) and you really don't want to mess around in that directory on your own.

 

You need to look into installers as they can take care of all these dependencies for you, and kick off the correct redistributable installers as well. If you want VS to place the right dlls into your exes build directory look into post build steps for VS.
 

Edited by NightCreature83
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0