C implementation of INI parsing routines (Ini_New, Ini_Dispose, Ini_ReadFromFile, etc.)

[AllenInIowa]

I had been building some command-line tools using LabWindows, but found that in order to run them, the system had to have the NI runtimes installed. For basic commands that didn't need any of the LabWindows-specific features, it makes more sense to just use GCC or some other compiler.

One of my command-line tools made use of the INI parsing routines like Ini_New(), Ini_Dispose(), Ini_ReadFromFile(), etc. so I could not move it to a diffferent compiler.

I decided to create a very simple implementation of the basic functions -- but really just the ones I was needed. If anyone else is in a similar spot, the code is free to use for any purpose (public domain):

allenhuffman/INIParser: LabWindows/CVI API-compatible read/write .ini files routines

I did this for fun on my own time, but with the ulterior motive that I will then appropriate the code to use for my work project.

[cbaxter]

It's not open domain, but the INI file handling is licensed with the CVI toolkit. You can find the sourcecode for it installed in the toolbox folder. On my system, that is located at

C:\Program Files (x86)\National Instruments\CVI2020\toolslib\toolbox\inifile.c

You may find other items you are trying to recreate in the nearby folders. As always, make sure it is being in a properly licensed manner.

[AllenInIowa]

---

@cbaxter wrote:

It's not open domain, but the INI file handling is licensed with the CVI toolkit. You can find the sourcecode for it installed in the toolbox folder. On my system, that is located at

C:\Program Files (x86)\National Instruments\CVI2020\toolslib\toolbox\inifile.c

You may find other items you are trying to recreate in the nearby folders. As always, make sure it is being in a properly licensed manner.

---

I had no idea sources were available.

Though, even if we could use this source in our own projects, I suppose that would not be the case when we move away from LabWindows and are no longer using it.

[ElectroLund]

Huh, interesting that this thread popped up so near my own.  In my case, using the toolbox INI functions inside my DLL project is creating a GPF when the DLL is used in a host application. 

So one solution for me is to use a 3rd party INI parsing lib.  Thanks, I'll have a look at it!

[ElectroLund]

Thank you for your INI lib contribution!  

I attempted to resolve my own issue with putting it inside my DLL project.  Curiously, I had the same issue with GPFing.  That's pretty wild to me. So I've abandoned the DLL approach for now.