AzCoder

Members
  • Content count

    82
  • Joined

  • Last visited

Community Reputation

150 Neutral

About AzCoder

  • Rank
    Member
  1. Choosing a laptop (considering MacBook)

    I've got a Macbook Pro. Frankly, I love it. Mac OSX is simply outstanding ( I also use Linux and Windows quite a bit. I am even a RedHat Certified Engineer). This MacBook Pro has a Radeon 1600. It is sufficient for my game dev needs. Supports GLSL and is fast enough. I cannot emphasize how well designed it feels. I use a monster Alienware laptop at work. I hardly ever use it since I got the macbook pro. My favorite feature is the backlit keyboard for late night coding... ;-) I like XCode quite a bit - but I also still use emacs/gcc/make BTW - Ruby development is also great on the mac. Now for the bad news... IMHO - The macbook non-pro does not have an adequate graphics card for game development work. You should get the MacBook Pro if you want to do any 3d work at all.
  2. Visual C++?

    After spending several years teaching c++ at the local community college, I have found another great (and free) option is to use gcc (Gnu Compiler Collection). Using the command-line compiler is slightly harder at first, but I think it imparts a much greater understanding of the development toolchain and process. It is easy for users of command-line compiler like gcc to switch to an ide and become very productive. On the other hand, I have found people who only know Visual C++ have a difficult time swithing to other ides and/or platforms. In the long run, early exposure to gcc results in a better understanding faster. The gcc/make/emacs toolchain is basically the same on Windows, Linux, Mac, Solaris, and others. This is key to facilitating cross-platform development. On Windows, you can both mingw and cygwin can help you get compiling with gcc quickly. If you are interested, you can find more info at: http://www.mingw.org/docs.shtml One last note - if after learning gcc you desire to use an IDE(many people do, including myself), Apple's XCode is another free and outstanding choice in addition to Visual c++. Happy Coding
  3. Most companies - like MS - don't ever release source. On the other hand, the source for quake 1,2, and 3 is available on the net. Just google for it.
  4. Is gentoo another distro?

    Gentoo is great. Portage is really slick. As an example, if you want emacs installed on your system: emerge emacs This downloads the source code for emacs and compiles it specifically for your system. If you want vi you type: emerge vi It is really easy(AFTER YOU GET IT INSTALLED). The ultimate developers box where everything is compiled by you for you. Plus the forum community is very active and helpful. Happy coding
  5. OpenGL OpenGL T&L ?

    You do not know whether or not T&L is used - the driver does it for you. Of course, You can probably tell by the framerate for a large scene. The driver can do it in hardware or software - it is up to driver writer. This applies to any of the features. An OpenGL driver conforms to a specification - not to an implementation technique.
  6. C++ compliler

    I had problems running c++ Visual Stuio 2006 apps on other machines (this requires more than just copying the .exe and dlls) Another option is to use gcc. gcc is the Gnu Compiler Collection. It is a command line compiler availible for Win,Linux,mac. It is a great choice for cross-platform development because it works on almost all platforms. The windows port of gcc is called mingw (Minimalist Gnu For Windows). www.mingw.org. Installing msys(availible from mingw) gives you a bash-like environment to compile from. The transition from a VB/windows mindset is a little different. Patience will pay off. The basic flow might be: Fire up msys, browse to home directory, create project directory. Fire up emacs create source file and Makefile. Compile with make. This exe you can copy and run from any machine. Happy Coding
  7. In terms of "looking professional", I do not see the API that you use for input having any impact at all. Almost all games use an API of some sort - even OpenGL and DirectX are nothing more than APIs exposing capabilities of the hardware. If you build your own cross-platform API for input, you would want to use the same api for other games you build. You could even let your buddy use it - just package it as an api. For that matter, you could name it SDL and make it public. Don't reinvent the wheel. My advice - spend your time building a great game instead of developing a cross-platform api. Good luck and Happy coding
  8. Red Hat Fedora questions

    gcc - The Gnu Compiler Colection is the compiler. There are several frotn-end ides you can use with it.
  9. Deploying C++ VS 2005 Apps

    I am using the Professional Edition not Express. I haven't changed any of the default settings other than to add additional libraries to the linker input. Are there any ways to identify a rogue dependency - shouldn't depends.exe find it. Googling revealed substantial activity on this subject - it seems it is a rampant problem.
  10. Recently I decided to try out VS 2005 for some c++ development. I have an existing cross-platform(windows/mac/linux) OpenGL demo I wanted to work on. Everything built and ran fine (eventually), but when it came time to run it on another machine, I got: "App has failed to start because the application configuration us incorrect. Reinstalling the application may fix the problem." I used depends.exe to determine any dependencies. I tried manually including msvcr80d.dll and other dependencies in the directory to no avail. I tried running vcredist_x86.exe on the target. Still no dice. Finally I built a setup.msi for my app. It wanted me to install the .Net framework on the target!!!!! This is madness. What are they thinking. I just have a simple native .exe. I want to target the commonly installed c-runtime. Why do they make this hard? Thanks in advance for any tips.....I am seriously thinking about returning to my happy mingw/emacs world where I can just copy the .exe to deploy.....
  11. [.net] OpenGL in .NET

    If portability is your goal, c# has several issues with it - number one being the monopolistic driving force behind it. Clearly, c# will run on linux/mac, although there is limited acceptance by either os community. I do not think you will see many significant applications built using c# for any platform other than Windows. On the other hand C/C++ has substantial use on all major platforms.
  12. [.net] OpenGL in .NET

    You are on the portability high-road using OpenGL and SDL. Your app will be easily ported to linux/mac. Using Visual Studio is also not a problem, as you already stated. The platform of your editor doesn't matter. Why tarnish your app with C# and .net....stick with c++ and keep portability(and performance for that matter). Just stay away from the MS Kool-Aid and vendor lock-in.
  13. Boost is worth the effort, although there is a learning curve. Check out a book on boost by Karlsson if you are interested in how to use some of the libraries. To install: Step 1: Download the zip and unzip it. Step 2: Get the prebuilt jam executable and unzip it. Put that directory in your path. (Edit Path by using Control Panel...System..Advanced....Environemnt Variables) Step 3: Open Visual Studio command prompt. Browse to boost directory. Run: bjam "-sTOOLS=vc-8_0" install (if using VS2005) That will build all the libraries. To use them in your project, edit your directories within VS using: Tools...Options....Projects and Solutions...VC++ Directories. The drop-down on the right controls whether you are changin include directories or lib directories. e.g. Add the boost directory to the list of include directories. Hope that helps.... Happy Coding
  14. What is the actual erro message? Also, does the user excecuting gcc have rights to the file?
  15. Inline functions

    Here is a direct discussion of this on msdn: http://msdn2.microsoft.com/en-us/library/feffc7b5.aspx Quote "You should exercise care when providing imported inline functions because they can create the possibility of version conflicts. An inline function gets expanded into the application code; therefore, if you later rewrite the function, it does not get updated unless the application itself is recompiled. (Normally, DLL functions can be updated without rebuilding the applications that use them.)" Happy coding