LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Repeat compile the main program

Solved!
Go to solution

Hi guys!

When I open my LVOOP project,then open the main program, it recompile every time.

This question has puzzled me for a long time.

any solution or workaround  in sight

 

0 Kudos
Message 1 of 7
(2,548 Views)

billko_1-1630183113744.png

And make sure to "Mark Existing Items".  By separating the source code from the compiled stuff, if the source code didn't change, LabVIEW won't make you have to save it.

 

To make this the default behavior for new projects, do this:

billko_0-1630182860364.png

 

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 2 of 7
(2,494 Views)

Hi billko!

Thanks for your reply.

My project settings and properties are exactly like what you said, and I set every vi in this project to separate compiled code from source vi , but the problem remains.

007hero_0-1630203482915.png

 

0 Kudos
Message 3 of 7
(2,479 Views)

I’ve had cases where a VI would always have an asterisk and I could never figure out how to get rid of it.  My best guess is that something in class or xinterface causing a lock somewhere.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 4 of 7
(2,464 Views)

@paul_cardinale wrote:

I’ve had cases where a VI would always have an asterisk and I could never figure out how to get rid of it.  My best guess is that something in class or xinterface causing a lock somewhere.


Unfortunately, I've seen this as well.  I was hoping for something simple.  I did notice that, in one of the projects like that, a LabVIEW base dependency kept changing, and I have no idea why.  If I opened the main VI and closed it, a dependency would change.  But if I saved it that way, the next time I opened the project (but not the VI), the dependency would revert.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 5 of 7
(2,456 Views)

thanks,guys.

I found a solution for my problem.

firstly,Cancel the setup of project property:Separate compiled code from new project items,then click Mark Existing Items button,unmask all items, close dialog and save project.finally, reopen the project, and restore all Settings.

The repeat compile problem will disappear.

it works,but  I still don't know the cause of this problem.

 

 

 

Download All
0 Kudos
Message 6 of 7
(2,433 Views)
Solution
Accepted by topic author 007hero

@007hero wrote:

thanks,guys.

I found a solution for my problem.

firstly,Cancel the setup of project property:Separate compiled code from new project items,then click Mark Existing Items button,unmask all items, close dialog and save project.finally, reopen the project, and restore all Settings.

The repeat compile problem will disappear.

it works,but  I still don't know the cause of this problem.

 

 

 


This could be explained by the "Separate compiled..." checkbox somehow got out of sync with that actual state of the VIs.  Maybe doing what you did forces an update of all the VIs, making them consistent with the checkbox again.  Just a guess.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 7 of 7
(2,403 Views)