Like Tree2Likes
  • 1 Post By Adak
  • 1 Post By CommonTater

difference between build and compile.

This is a discussion on difference between build and compile. within the C Programming forums, part of the General Programming Boards category; a few days back i was ambushed here for saying that i used turboC . so now i have downloaded ...

  1. #1
    Registered User
    Join Date
    Aug 2011
    Posts
    91

    difference between build and compile.

    a few days back i was ambushed here for saying that i used turboC .

    so now i have downloaded pelles c.

    but there are a lot of options compared to tc.

    please tell me the following:

    whats the difference between build and compile.?

    difference between build and rebuild?.

    in tc i can trace a program by simply pressing F7 what should i use here?

  2. #2
    Registered User
    Join Date
    May 2011
    Location
    Around 8.3 light-minutes from the Sun
    Posts
    1,866
    Step 1: Read the helpfile.
    Step 2: Read the helpfile.
    Step 3: Read the helpfile.
    Quote Originally Posted by anduril462 View Post
    Now, please, for the love of all things good and holy, think about what you're doing! Don't just run around willy-nilly, coding like a drunk two-year-old....
    Quote Originally Posted by quzah View Post
    ..... Just don't be surprised when I say you aren't using standard C anymore, and as such,are off in your own little universe that I will completely disregard.
    Warning: Some or all of my posted code may be non-standard and as such should not be used and in no case looked at.

  3. #3
    Registered User
    Join Date
    Aug 2011
    Posts
    91
    i got answers to this if anybody else wants it please visit:

    Difference between Build, Rebuild & Compile My Thoughts & Views

    but how to trace still remains unknown.

  4. #4
    Registered User
    Join Date
    Sep 2006
    Posts
    8,868
    I'm pretty new with Pelles C, (former long term Turbo C user). This is how I do it:

    1) Click on Project tab, >> project options, >> and compiler tab

    2) Change the debug information option from "none" (the default), to "full".

    3) Click on linker tab. Change debug information from "none" to "CodeView & COFF format".

    Click on the Save button at the bottom of the page, and build your project with those settings.

    Right now, I don't recall if you have to save the settings after making the step 2 changes, and save them again after making the step 3 changes, or if just the one time, after step 3, is sufficient.

    Click on the icon of the stepping you want in the top banner of icons.
    Last edited by Adak; 08-18-2011 at 11:20 PM.
    theju112 likes this.

  5. #5
    Registered User
    Join Date
    Aug 2011
    Posts
    91
    sorry if my question is not clear.by tracing i meant a step by step execution of the program.

    for that i found out that we can simply click debug and click on step in icon.

    but i followed your steps and now some useful information is being displayed at the bottom after i
    compile.
    thanks for that tip.

  6. #6
    Registered User
    Join Date
    Sep 2006
    Posts
    8,868
    Interesting. When I don't include the debug info into the program, and set the linker option as I mentioned, I see a warning about not having any debug info in the program, and then a full page of assembly instructions appears - no C language anymore. I can trace the program execution - but I don't know very much about assembly, and I don't want to program in assembly, either. I'm guessing you have a slightly later version of the Pelles C compiler, maybe.

    I found the add line numbers option to be useful, and clicking on the line creates a breakpoint when you're in debug mode. Then there is a Quick Watch icon that's handy at the top right hand side of the top banner.

  7. #7
    Banned
    Join Date
    Aug 2010
    Location
    Ontario Canada
    Posts
    9,547
    Quote Originally Posted by theju112 View Post
    sorry if my question is not clear.by tracing i meant a step by step execution of the program.

    for that i found out that we can simply click debug and click on step in icon.

    but i followed your steps and now some useful information is being displayed at the bottom after i
    compile.
    thanks for that tip.
    Ok, now listen to me VERY carefully.... This is a bit different than you're used to...

    1) Compile means generate an object file from source code...
    2) Build means to both compile and link to generate an executable, library or DLL
    3) Rebuld erases the existing object and executable files and rebuilds the project from scratch.

    Now here's the part you won't be used to doing, but it is an absolutely essential step if you are ever going to get the hang of Pelles C...


    Are you ready?


    In the top menu bar you will see the word "Help" ... Now I want you to click on that...
    Now in the resulting help menu ... Click on "Contents"....

    Now start reading.

    Yes that's right... READ THE EFFING HELP FILE... Pelles C comes with the best and most detailed help file I've ever seen. Almost anything you would want to know about C-99 or POIDE is in there, explained in full detail.
    Last edited by CommonTater; 08-19-2011 at 06:54 AM.
    manasij7479 likes this.

  8. #8
    Banned
    Join Date
    Aug 2010
    Location
    Ontario Canada
    Posts
    9,547
    Quote Originally Posted by Adak View Post
    Interesting. When I don't include the debug info into the program, and set the linker option as I mentioned, I see a warning about not having any debug info in the program, and then a full page of assembly instructions appears - no C language anymore. I can trace the program execution - but I don't know very much about assembly, and I don't want to program in assembly, either. I'm guessing you have a slightly later version of the Pelles C compiler, maybe.
    That's because you aren't writing line markers into the PE Image so there's no way to track your source against the final executable... That particular arrangement is useful with external debuggers such as winDebug or OllyDebug that work on the PE image directly.

    I found the add line numbers option to be useful, and clicking on the line creates a breakpoint when you're in debug mode. Then there is a Quick Watch icon that's handy at the top right hand side of the top banner.
    All of which are explained in the help file...

    Help->Contents->Integrated Environment->POIDE Integrated Environment->Debugger
    Last edited by CommonTater; 08-19-2011 at 07:16 AM.

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. how to build AST ?!
    By Meshal in forum C Programming
    Replies: 7
    Last Post: 12-13-2006, 05:05 AM
  2. non dot net build
    By luigi40 in forum C# Programming
    Replies: 11
    Last Post: 11-08-2005, 03:11 PM
  3. 0 compile error but 2 build error. need help please!
    By jibbles in forum C Programming
    Replies: 5
    Last Post: 08-30-2004, 04:30 PM
  4. Compile vs. Build
    By Yawgmoth in forum C++ Programming
    Replies: 1
    Last Post: 01-04-2003, 04:30 PM
  5. Build my own *.lib
    By Markitos in forum C Programming
    Replies: 1
    Last Post: 10-31-2001, 04:22 PM

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21