Particle Dev: Build didn't produce binary Error

[sazp96]

Hello folks,

Starting today, code that I was able to successful compile yesterday it is failing to do so today. I’m compiling on the cloud.

Particle Dev gives me a truncated error that says:
Build didn't produce binary Error: Command failed: /spark/c...

I read some other threads and I can confirm that there are no other ino files in the build directory.

I’m able to compile simpler smaller programs. But the one I’m trying to compile (the binary was around 100k) fails to do so.

During yesterday’s upgrade to the compiler, was there a size limit, or compilation time out limit implemented?

Any other ideas of what could be causing this error?

Thanks!

[photonizer]

Hi,

I have same error today with code that worked few days ago.
My binary was 77k.

I have UHD resolution and if I maximize Particle Dev window, I can see error:
Build didn’t produce binary Error: Command failed: /spark/compile_service/shared/workspace/6_photon_0.4.6_19_1/firmware/…

Maybe there is just problem on the server side.

[photonizer]

SOLVED

I found this post:

Error: no matching function for call to 'CloudClass::variable

Hi @wmoecke The two lines above are in error: you should not have the “&” for a string (char array) and a recent compile time check was put in to enforce this. This is probably the number one cloud coding error I see here so I am happy to have the check in place.

My code had: "Spark.variable("result", &resultstr, STRING);"
I changed it to "Spark.variable("result", resultstr, STRING);" and compile started to work!

[BulldogLowell]

@photonizer, glad you found your error in the code.

It would be nice if Particle Dev generated a less cryptic response!

I don’t know if Particle Dev is current with the latest firmware release. @suda ?

[LukeUSMC]

There is a bug open on the lack of detail in compiler errors when using Particle-Dev. I think @mdma is working it. Bug #79 and #110 are both related.

[ScruffR]

@photonizer, @sazp96

Just to be prepared if some other “cryptic” messages pop up in future, due to the transition from Spark.IO to Particle.IO a while back the keyword Spark will be deprecated and changed over to Particle.
So try to already replace things like Spark.function() with Particle.function() - currently it should work both ways on the Core but I don’t think the old version still works on the Photon.

[sazp96]

@photonizer, thanks for pointing me out to the variables. As soon as I commented out my string Particle.variable() my code compiled again.

@ScruffR, I have updated all my Spark. to Particle.. It was about time to do it.

Has Particle.variable stop supporting the String class? The code below generates the “Build didn’t produce…” error:

String varMyIP = "000.000.000.000";
...
Particle.variable("PublicIP", varMyIP, STRING);

[BulldogLowell]

look here:

Particle Device OS Updates Thread

API Changes in 0.4.6 Please note that the Particle.variable() API was changed to include stricter checks for variables. If you see a compiler error on code that has previously worked, this is an indication that the code wasn’t calling the API correctly. For reference, the 3 types of variables are declared like this: char string_variable[30]; // change 30 to be as large as is needed to store the string value int int_variable; double double_variable; Particle.variable("string", string_variable…

you'll want to use a C string

[ScruffR]

Just as a side note about String and Particle.variable()

Photon command line build failure

Have a look here Particle Firmware Updates Thread Help creating STRING variables It never was a good idea to use a String object for a Particle.variable() since the actual stored string might get relocated causing the “link” between the string and the Particle.variable() to break. Before you weren’t warned about the risk, but it would have happened. Now you get told beforehand that this may break your code and hence will not build. Sorry I must be reading over it, where is the spelling mis…

Even if it works at some point it might stop working under some circumstances and errors like that are a hell of a job to find.

[sazp96]

Thank you @BulldogLowell and @ScruffR. I will do the switch to C string.

[zebrone92]

Hi,
I’m trying to run from Particle Dev, a software on the Photon, but I’m getting the “Build didn’t produce binary error”. How Can I fix it? The software is .ino extension.

[sazp96]

There are a few things that can cause this error.

One that we keep bumping into is the size of our binary. How many kb was the last binary you were able to compile? If your new binary is greater than 128kb you would get this error.

[rickkas7]

Another cause of “Build didn’t produce binary” with no error listed is that the directory containing the .ino file contains more than one .ino file. It doesn’t just build the file you have open, it builds all of the .cpp and .ino files in that directory so you can use libraries.

[ScruffR]

And a number of other reasons discussed in the forum.

Usual response:
Provide more background, code, screenshot, … to save us from needing to guess around

Just a few
Particle Dev won't build, particle-cli will
Particle Dev: "build didn't produce binary"
Particle Dev with multiple projects - what?
Particle dev will not compile
Particle Dev objbase.h no such file Cannot compile

Mostly the same reasons

[zebrone92]

@rickkas7

Particle Dev: "build didn't produce binary"

Thank you for your reply. In my project there a some different library, so I have multiple cpp and h file, with just one .ino file. I always get that problem...

[Glenn]

I had this same problem today and after I chose a device, the error went away. For those with no compile problems perhaps this would help with your issue.

[grantka]

I had this problem and the actual issue was a particle.function with too long of a name (12 character max). Hope this helps someone.

[ScruffR]

What version were you targeting?
AFAIK with more recent versions you should get an explicit warning/error when providing too long names.
If this wasn’t the case with the most recent version, we might have found a regression.

But I do get

In file included from ../wiring/inc/spark_wiring.h:48:0,
                 from ./inc/application.h:36,
                 from _inttest.cpp:2:
../wiring/inc/spark_wiring_cloud.h: In instantiation of 'static bool CloudClass::function(const T&, Types ...) [with T = char [14]; Types = {int (*)(String)}]':
_inttest.cpp:25:41:   required from here
../wiring/inc/spark_wiring_cloud.h:188:9: error: static assertion failed: 

In Particle.function, name must be less than 12 characters

Although it should actually be In Particle.function, name length must be equal or less than 12 characters

[grantka]

I was targeting 0.5.3

[vicatcu]

I’m also getting this error, using an brand new Electron 2G. When I click on the message, Particle-dev tells me “There were no compile errors.” My project has a .cpp and .h file in the project directory alongside my .ino file, which has a #include “mylib.h” at the top of it.

Using Particle-dev to comipe and generate a binary seems to work fine on a trivial stand alone .ino file in its own directory (i.e. with an empty setup and loop).

Are multi-file projects just not yet supported in Particle-dev? This documentation would lead me to believe it was…