Author Topic: vctoolkit: Cannot open input file 'SDL.obj'  (Read 5876 times)

New User

  • Guest
vctoolkit: Cannot open input file 'SDL.obj'
« on: May 21, 2005, 02:56:58 am »
Trying to compile an the default project for sdl, and I get that error. I was using visual studio 6 and added the include path and lib paths. Anyone know how to fix this? Never encountered this problem with sdl with dev-c++ or visual studio.

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
vctoolkit: Cannot open input file 'SDL.obj'
« Reply #1 on: May 21, 2005, 04:28:32 am »
As you've been noticing, most of our project templates are created by trial-and-error :oops: . How about creating a sample SDL project in dev-c++, importing it from Codeblocks and then posting here the contents of the .cbp file?

Anonymous

  • Guest
vctoolkit: Cannot open input file 'SDL.obj'
« Reply #2 on: May 21, 2005, 06:12:53 am »
Not too sure if the -lmingw32 will cause problems using the vctoolkit compiler.... Here is the cbp file:

<?xml version="1.0"?>
<!DOCTYPE Code::Blocks_project_file>
<Code::Blocks_project_file>
   <FileVersion major="1" minor="1"/>
   <Project>
      <Option title="Project1"/>
      <Option makefile="Makefile"/>
      <Option makefile_is_custom="0"/>
      <Option compiler="1"/>
      <Build>
         <Target title="default">
            <Option output="C:\Dev-Cpp\SDL.exe"/>
            <Option working_dir="."/>
            <Option object_output=".objs"/>
            <Option deps_output=".deps"/>
            <Option external_deps=""/>
            <Option type="1"/>
            <Option compiler="0"/>
            <Option projectResourceIncludeDirsRelation="1"/>
         </Target>
      </Build>
      <Linker>
         <Add library="mingw32 -lSDLmain -lSDL"/>
      </Linker>
      <Unit filename="main.cpp">
         <Option compilerVar="CPP"/>
         <Option target="default"/>
      </Unit>
   </Project>
</Code::Blocks_project_file>

Anonymous

  • Guest
vctoolkit: Cannot open input file 'SDL.obj'
« Reply #3 on: May 21, 2005, 06:21:25 am »
And now this:

Project   : Project1
Compiler  : Microsoft Visual C++ Toolkit 2003 (called directly)
Directory : C:\Dev-Cpp\
--------------------------------------------------------------------------------
Switching to target: default
Compiling: main.cpp
Command execution failed...

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4291
    • Code::Blocks IDE
vctoolkit: Cannot open input file 'SDL.obj'
« Reply #4 on: May 21, 2005, 09:40:39 am »
Quote
As you've been noticing, most of our project templates are created by trial-and-error

This is *so* untrue...

Quote
Switching to target: default
Compiling: main.cpp
Command execution failed...


Enable the C::B debug log (Settings->Environment), restart C::B, recompile your project and when the "Command execution failed..." message appears, switch to the "Code::Blocks Debug" message tab and see what command is failing to execute. Please post this command here.

Have you tried compiling other stuff? Only the SDL template behaves like that?
I 'm asking because, usually, the "Command execution failed..." message appears when C::B is badly configured.

Create a new console project and build it. Does it build or not?

Yiannis.
Be patient!
This bug will be fixed soon...

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4291
    • Code::Blocks IDE
vctoolkit: Cannot open input file 'SDL.obj'
« Reply #5 on: May 21, 2005, 09:44:45 am »
On a sidenote, keep in mind that although C::B comes with various templates (like wxWidgets, SDL, etc) it doesn't provide the necessary headers and libraries for them...

Yiannis.
Be patient!
This bug will be fixed soon...

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
vctoolkit: Cannot open input file 'SDL.obj'
« Reply #6 on: May 21, 2005, 05:31:40 pm »
Quote from: mandrav
This is *so* untrue...


Whoops, there goes my big mouth again :oops:.

Um what I meant to say is that our templates aren't tested in ALL configurations, so we might skip a few errors here or there...

:oops: In any case, that's what the community is for: To improve and help each other :)