user28950: I am using the ESP8266 board manager. I want to see how Arduino IDE compiles my code once I click Verify.
Why do I want to do this?
I am trying to integrate a C library for which there is now Arduino library package available. So I have to integrate it from source. I want to be able to specify custom -I, -L  and -l flags when I compile my code.

user4169: In the Arduino IDE switch on File>Preferences>Upload erbose and Compile Verbose
When you build you will see all the compiler commands
The verify is often a -v param in the command
You will find the esp8266 platform.txt in a location such as c:\users\[name]\appdata\local\arduino15\packages\esp8266...
The platform.txt contains all the compiler switches, the boards.txt in the same location can also contain board specific switches.
You can not specify different switches for different files in a compilation but you could compile your code into an archive then force it into the build process. Not sure if that is practical or not.

28950: <p>I am using the ESP8266 board manager. I want to see how Arduino IDE compiles my code once I click Verify.</p>

<h3>Why do I want to do this?</h3>

<p>I am trying to integrate a C library for which there is now Arduino library package available. So I have to integrate it from source. I want to be able to specify custom <code>-I</code>, <code>-L</code>  and <code>-l</code> flags when I compile my code.</p>
 4169: <p>In the Arduino IDE switch on <code>File</code>><code>Preferences</code>><code>Upload erbose</code> and <code>Compile Verbose</code></p>

<p>When you build you will see all the compiler commands</p>

<p>The verify is often a <code>-v</code> param in the command</p>

<p>You will find the esp8266 platform.txt in a location such as <code>c:\users\[name]\appdata\local\arduino15\packages\esp8266...</code></p>

<p>The <code>platform.txt</code> contains all the compiler switches, the <code>boards.txt</code> in the same location can also contain board specific switches.</p>

<p>You can not specify different switches for different files in a compilation but you could compile your code into an archive then force it into the build process. Not sure if that is practical or not.</p>
