• 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
fir

ling obj+obj to obj and 'where headers'

2 posts in this topic

I got 2 practical questions (reffering to gcc/mingw)

 

I got a set of many obj (.o) files can I link them into other biger obj

file? (as an intermediate step later I will be linking this bigger obj's into exe)

 

I got some header "all_headers.h" file containing references (includes) from all my header files (i know its bad name but I cannot find some better)

 

If I want to add it to my files I could use relative like

 

#include "..\all_headers.h"

or 

#include "c:\code\all_headers.h"

 

but both are somewhat wrong 

could I just include

 

#include "all_headers.h"

or

#include <all_headers.h>

 

and make precompiler to find it? (but i dont wont to copy this all_headers.h

out of my source folder to increase dependency confusion just to inform

compiler where ha can search for it ?)

 

tnx

 
 

 

 

 

 

0

Share this post


Link to post
Share on other sites

I got a set of many obj (.o) files can I link them into other biger obj
file? (as an intermediate step later I will be linking this bigger obj's into exe)

Yes, at least with a link format like ELF, but it's generally not done. Usually if you want to group compiled .o files into a single "bundle" you use a static library. Everything is set up to support that, and it works with all link formats.

I got some header "all_headers.h" file containing references (includes) from all my header files (i know its bad name but I cannot find some better)
 
If I want to add it to my files I could use relative like
 
#include "..\all_headers.h"
or 
#include "c:\code\all_headers.h"
 
but both are somewhat wrong

It's wrong on 2 levels: (1) it's wrong because '\a' and '\c' are not valid characters to include in pathnames, and (2) using relative paths is bad practice becuase it makes work when you refactor your project, and it's not necessary. Certainly hardcoding the drive name into a path is going to bring you grief sooner or later.

It's not unusal to namespace headers, which uses paths relative to the top of a source tree. Relying on platform-specific behaviour like the dot-dot directory being the parent of the directory in which the current source file is found will break.

could I just include
 
#include "all_headers.h"
or
#include <all_headers.h>
 
and make precompiler to find it? (but i dont wont to copy this all_headers.h
out of my source folder to increase dependency confusion just to inform
compiler where ha can search for it ?)

Yes, that is how things are designed to work. The command-line switch for extending the search path for header files is -I (upper-case letter "i").
1

Share this post


Link to post
Share on other sites

OK, tnx this " -I path " seem to work,

 

Dont you know maybe the first?

 

g++ src1.o src2.o -o dst.o will link to obj only?

 

anyway when speaking about hard paths and burden of refectoring work

moving the paths to build scripts out of source is also maybe not quite ideal when refactoring (and at this project i am constattly refactoring 

filenames and folder names so tjis is still a burden - but i will use this way -I ..\ nothing better dont come to my mind

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