NO

Author Topic: Linker Bug?  (Read 1755 times)

John S. Kent

  • Guest
Linker Bug?
« on: October 08, 2019, 06:53:13 PM »
Bug: ? & documentation not found

   I am completely new to the Pelles C tools.

   I started with the standard "Hello World" as a console application.

   Your first project: Hello, World. The Help Documentation has some
   language issues. See Help for "Integrated Environment"
   subsection: "POIDE integrated environment"

   The Images of the "Win32 application wizard: Step 1 of 2" &
    "Win32 application wizard: Step 2 of 2"
   Has the Dialog button labels in a non-English language.
   Localization is difficult!, detailed, & complicated.

   Getting past the documentation, the actual IDE Dialog components
   are all in the same language (English in my case).

   I got to the Project Menu & the Build "HelloConsoleApp.Exe".
   The source code file was "main.c" @ the time. I was able to compile
   main.c. However the linker failed. The problem turned out to be an
   issue with how the pathnames of the files are handled (& modified?).

   My original path was E:\John's\Pelles C Projects\HelloConsoleApp

   The Project output showed the above as:
   E:\John's\Pelles C Projects\HelloConsoleApp\main.c

   The linker failed; unable to find main.obj, it showed the path as

   E:\Johns\Pelles C Projects\HelloConsoleApp\output\main.obj

   See the problem?

   I changed the pathname to e:\Pelles C\HelloConsoleApp\

   Still miffed; Notice "John's" as opposed to "Johns". The IDE
   is improperly handling pathnames. I have fallen into these
   localization trap a few times.
   
   I now have 26 running applications.  Built with Pelles C IDE.
   I also use the Embarcadero C compiler (Borland) to build these
   same programs.

   Now moving on. where is the documentation that details the Pelles &
   Microsoft language extensions. List of functions? ... other features?

   I can not find that information anywhere in the documentation.
« Last Edit: October 14, 2019, 06:14:18 PM by John S. Kent »

Offline Pelle

  • Administrator
  • Member
  • *****
  • Posts: 2266
    • http://www.smorgasbordet.com
Re: Linker Bug?
« Reply #1 on: October 13, 2019, 10:47:30 PM »
   The Images of the "Win32 application wizard: Step 1 of 2" &
    "Win32 application wizard: Step 2 of 2"
   Has the Dialog button labels in a non-English language.
   Localization is difficult!, detailed, & complicated.
When this picture was made, it was impossible for my Swedish Windows version to display English (buttons). Considering only a handful of people will probably ever read this part of the documentation anyway, it seemed like a waste of time hand-editing the images (the text tells you what to do, and it's a standard Windows Property Sheet so it shouldn't be too surprising what to do, no?).

   Now moving on. where is the documentation that details the Pelles &
   Microsoft language extensions. List of functions? ... other features?
Well, the help page for the compiler project options ("Project" -> "Project options" -> "Compiler" and press "F1"), "IDE: Compiler project options dialog" says:
- for "Enable Microsoft extensions": see /Ze option (a hyperlink to be clicked).
- for "Enable Pelles C extensions": see /Zx option (a hyperlink to be clicked).
Those pages (for the /Ze option and /Zx option) will list the C language changes.

For C runtime functions, look under the "Content" tab in the help file. Everything under "Standard C #include files" is for standard C, everything under "Private #include files" is extensions of some kind (click enough "+"-signs to see extended functions, listed per #include file).


/Pelle

John S. Kent

  • Guest
Re: Linker Bug?
« Reply #2 on: October 14, 2019, 05:20:01 AM »
"Private #include files" That will take a few weeks to read & digest!!! Incredible amount of information! large number of functions, data types, macros, etc.  Extensive Extensions!

"Privata # inkludera filer" Det tar några veckor att läsa och smälta !!! Otrolig mängd information! stort antal funktioner, datatyper, makron osv. Omfattande tillägg

Google-översättning fungerar bra om man också kontrollerar den bakåtvända översättningen