Are you using .1751 or .1761? There were some issues with references in .1751 that where fixed in last week’s update.
For code completion, you can/must right-click the file or the whole project and choose “work in” to set which context you want to work in. Since CC will of course depend on the target project.
Oh, I didn’t know there’s an updated Fire!
UPD. I’ve just updated Fire and now referencing via drag’n’drop is working like a charm 
I just updated to 1761, but Eunit is still not working for me 
It is unable to find libEUnit.fx. The project I created is the Eunit project for iOS.
@mh @rudyryk Can you check it and see if it is working for you?
1 Like
When I right click and hover on work in, I get ‘None’. Also as I type I get an error which says the cc will work after parsing is complete. Here are the screenshots. Any Clues?
.
Hmm. does the the static library project have a reference to the shared project, yet?
Yes it does. I used @rudyryk 's method to add the reference by editing the .elements file. Does that make a difference?
No, that should work, then. can you post or email me your project, so i can have a look to see if it’s something specific to this project? it should look something like this: Image 2015-05-17 at 1.05.14 PM
Done! I’ve messaged you on this site. If you can also help me with EUnit then that’ll be awesome! Thank you
I don’t see the shred project referenced on the solution you sent: Image 2015-05-17 at 6.54.38 PM (instead, you dip have the source file included in the library project). After i add the reference, the Work in menu works ok.
That’s odd. i can add a reference to it fine and it builds, your project. Can you turn on Detailed logging and post/send me a build log? I take it libEUnit.fx does show in the Add References dialog? Does the EUnit folder show black (red means missing) in Preferences? http://share.dwarfland.com/azxO
—marc
@mh After dragging the project to the references in 1761 I can see the project in the “work in” although cc isn’t working for me. As I type something, it just says “nothing to complete” are you facing the same?
this is what I see when i go to the preferences pane for Fire. The entire LibEUnit path is missing for me. How can I add it ? Thank you.
It’s working ok for me, e.g.: Image 2015-05-18 at 8.31.46 AM
Hmm, curious. now that i look at i again, it seems the oath i have set up is from the external compiler, but EUnit is not configured properly from within the Fire distro itself. In fact, it looks like we don’t even ship EUnit inside fore at all. that’s something i need to fix. It’s odd that EUnit shows at all in Add References, then (does it? of if not, how did you add it)
For now, id say remove the reference, then locate libEUnit,fx wherever you have your copy (i assume you maybe got it from git?) and tag that in from Finder into the project. that should add the reference with a hardcoded path and get you going for now.
I’ll fix for Fire to include EUnit properly, for the next beta.
yours,
marc
1 Like
Strange I just restarted Fire and its working now!
It does not show for me in the Add Reference both in Other References as well as System References. I added it by creating a new Eunit project for Cocoa and it creates this project but is unable to find LibEUnit.fx
Where can I get the LibEunit from? Do you guys have a git repo I can get the file from?
Actually the easiest option is to just grab and install the external compiler, it will will install and register it so Fire can find int too: http://docs.elementscompiler.com/Fire/Setup/ExternalCompiler/
Hmm, i thought we did, but looks like it’s not join github yet, but still in or private Git. i’ll see if we can get that addressed, soon.
thanx,
marc
okay so I got the external compiler and got it setup and running. It seems to have found LibEunit but now I’m having this issue in building the project. It seems that some Microsoft Build Utilities is not found. How can I fix this?
Don’t set Fire to use the external compiler. Just install it to get lbEUnit registered, but keep Fire set to using the internal compiler. (You probably have Mono 4 installed externally, and Mono 4 broke everything, by dropping support for MSBuild 3.5. We’re working around that, but Elements 8.1 will require Mono 3.x). Sorry about that, i should have been more explicit.
The tutorial suggested that Mono is a prerequisite so I went ahead and installed it as I was not sure if it was already installed.
The good news is that the build works fine and the LibEunit reference is also fixed! I’ll write some unit tests and update here as I build my library.
Is there a Sugar class that handles cross platform Json Parsing? If not, how can write one so that I can contribute it to Sugar on Github?
I moved 3 posts to a new topic: Contributing JSON support to Sugar
I moved 4 posts to a new topic: Warning on upper-case “Sugar” namespace in Java
I moved a post to a new topic: Sugar HTTP