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

vsc++:soil.lib linking problem

4 posts in this topic

hi

my previous program ran just fine, including the soil lib. but after i modified the program from pop to oop, i got the following errors.

1>------ Build started: Project: Fractals with zoom, Configuration: Release Win32 ------
1> Utilities.cpp
1>Utilities.cpp(124): warning C4996: 'fopen': This function or variable may be unsafe. Consider using fopen_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
1> c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\stdio.h(234) : see declaration of 'fopen'
1>Soil.lib(SOIL.obj) : warning LNK4075: ignoring '/EDITANDCONTINUE' due to '/OPT:ICF' specification
1>LINK : warning LNK4098: defaultlib 'MSVCRTD' conflicts with use of other libs; use /NODEFAULTLIB:library
1>Fractals with Zoom.obj : error LNK2001: unresolved external symbol "void __cdecl debug(void)" (?debug@@YAXXZ)
1>C:\Users\rob\DevC++ source\MSVC++\freeglut\fractal\Dynamical system and fractals\Fractals with Zoom\Release\Fractals with zoom.exe : fatal error LNK1120: 1 unresolved externals
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

any help will be appreciated.
0

Share this post


Link to post
Share on other sites
I'm not familiar with soil.lib, but you clearly miss a dependency for a function call probably looking similar to "debug ();" in file probably called "Fractals with Zoom.cpp".

My guess is that the named function only exists in debug mode (which makes sense, given the name ;-) ). Does it link in debug mode?

If so, following these steps to resolve the issue:

1) Open "Fractals with Zoom.cpp" ind Visual Studio
2) Switch to Debug|Win32 configuration
3) Find the call to "debug();"
4) wrap the function call like this:
[source lang="cpp"]#ifdef _DEBUG
debug ();
#endif
[/source]
IIRC, Visual C++ defines _DEBUG by default in Debug configurations, so you should be able to use it. If , however, you undefined this for some reason, use whatever you defined in its place.

Hope that helped.
0

Share this post


Link to post
Share on other sites
[quote name='nickme' timestamp='1355898183' post='5012349']1>LINK : warning LNK4098: defaultlib 'MSVCRTD' conflicts with use of other libs; use /NODEFAULTLIB:library
1>Fractals with Zoom.obj : error LNK2001: unresolved external symbol "void __cdecl debug(void)" (?debug@@YAXXZ)
1>C:\Users\rob\DevC++ source\MSVC++\freeglut\fractal\Dynamical system and fractals\Fractals with Zoom\Release\Fractals with zoom.exe :
[/quote]

While the missing debug() is indeed a problem, a more serious problem is the warning about MSVCRTD. Either you are mixing Debug and Release runtimes or you are mixing /MT and /MD builds. While it is indeed possible to use /NODEFAULTLIB to suppress the warning, this will not be enough in most cases and the program will crash (either persistently or weirdly and infrequently).
When [b]statically[/b] linking C++ code together you must ensure the participating code was generated with compatible settings. In case of MSVC, one of the most frequent candidates for such incompatibility are the /MT, /MTd, /MD and /MDd switches, which is usually visible by the generation of a LNK4098.
1

Share this post


Link to post
Share on other sites
[quote name='BitMaster' timestamp='1355911007' post='5012387']
While the missing debug() is indeed a problem, a more serious problem is the warning about MSVCRTD. Either you are mixing Debug and Release runtimes or you are mixing /MT and /MD builds. While it is indeed possible to use /NODEFAULTLIB to suppress the warning, this will not be enough in most cases and the program will crash (either persistently or weirdly and infrequently).
[/quote]

Hm, yes, I concur. But I think this warning will go away once the error is fixed, because it might well be something connected with the objectionable function that drags in the debug runtime. Either that, or the problem is simply that "Fractals with Zoom.obj" IS in fact the object file compiled in debug mode... Maybe no proper cleanup? But how you would provoke such behavior is beyond me...

But now that I thought that through once again, this seems even more probable.
0

Share this post


Link to post
Share on other sites
[quote name='sgt_barnes' timestamp='1355910184' post='5012382']
I'm not familiar with soil.lib, but you clearly miss a dependency for a function call probably looking similar to "debug ();" in file probably called "Fractals with Zoom.cpp".

My guess is that the named function only exists in debug mode (which makes sense, given the name ;-) ). Does it link in debug mode?

If so, following these steps to resolve the issue:

1) Open "Fractals with Zoom.cpp" ind Visual Studio
2) Switch to Debug|Win32 configuration
3) Find the call to "debug();"
4) wrap the function call like this:
[source lang="cpp"]#ifdef _DEBUG
debug ();
#endif
[/source]
IIRC, Visual C++ defines _DEBUG by default in Debug configurations, so you should be able to use it. If , however, you undefined this for some reason, use whatever you defined in its place.

Hope that helped.
[/quote]

what happened was that i previously have a funciton called debug(), and i deleted it implementation but did not the calling. the compiler did not generate a unidentifier error but must had tried to call other system debug() method. after i deleted all the debug(), it ran just fine now.

thank you all.
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