Home/ Questions/Q 8521851
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T06:56:37+00:00

Recently I had to use this command in a makefile I had for an

  • 0

Recently I had to use this command in a makefile I had for an sqlite program I’m working on:

gcc -g -c sqlite3.c -o sqlite3.o
g++ -g -c main.cpp -o main.o
g++ sqlite3.o main.o -o sqliteex

I had to directly compile the sqlite3.c file into my program in order to use the sqlite3.h interface (included in the main.cpp file with #include SQL/sqlite3.h). But why did I need to use gcc to do this and create sqlite3.o, then compile both files as .o files into my executable?

Edit: My guess would be that .o files are compilable by both gcc and g++, if this is the case, is it a good practice to just always compile things as .o files?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    But why did I need to use gcc to do this and create sqlite3.o, then compile both files as .o files into my executable?

    You did not need to do that. The reason you did do that was to specify that sqlite.c was C code and not C++ code. You could have done this instead:

    g++ main.cpp -x c sqlite3.c -o sqliteex

    Additionally, it is possible (but not at all certain) that the sqlite code could have compiled as C++, like this:

    g++ main.cpp sqlite3.c -o sqliteex
    • 0