I'm trying to work on a project on scala IDE but I've having build problems on scala IDE.
On sbt the project builds fine. I used the eclipse sbt plugin and imported the project on scala IDE. There were build errors, which makes the ide close to useless.
One of the errors is Compiler plugin paradise_2.12.1-2.1.0.jar is cross-compiled with incompatible version for this project: 2.12.1 vs 2.12.2
I thought scala minor versions were compatible, though I see there is an exception for some experimental modules. Is the macro paradise plugin one of those exceptions?
How can I fix it? Can I tell scala IDE to use 2.12.1? Shouldn't the sbt eclipse plugin take care of that? Should I report a bug(to which project)?
The project on which I'm working defines scala version to be "2.12.1", but I'd rather not change it. I'm using scala ide version 4.6.1.
here's the settings to change the scala compiler
right click on your project -> choose "properties"
from the menu tree on the left select 'Scala compiler'
check "use project settings" if unchecked
select the appropriate Scala installation from the 'Scala Installation' drop down
close the project properties window
rebuild project
my personal peeve is that when I run the eclipse plugin command from sbt, it always resets the scala installation for my project to "
Latest 2.12 bundle (dynamic)" so I've gotten pretty use to manually resetting my scala compiler version (along with my build path source directories).
If you need to (re)set your scala library container you can also do this in the project properties window (via the "Java Build Path" -> Libraries section). You may need to do this if you don't have an explicit fixed 2.12.1 installation available as an option in the above drop down.
Related
I followed Building From Source https://github.com/primefaces/primefaces/wiki/Building-From-Source instructions. Building the SNAPSHOT version project from command works well.
However, importing it into eclipse using the Existing Maven Projects wizard gives me a lot of errors in the Problems view. I fixed the lifecycle mappings by setting all to ignore.
I realized the generated source code in the target/generated-sources/maven-jsf-plugin directory but it was not picked up by the m2e plugins as a source folder automatically. So I included it into the eclipse build path manually. But then again, many compile errors show up in the generated code.
Does anybody use eclipse as IDE for primefaces development? How do you setup the eclipse project to develop primefaces?
The eclipse project uses Java Compiler compliance level 1.5 derived from the pom.xml maven-compiler-plugin settings. Setting the Java Compiler compliance level to 1.6 solved the issue for me.
I would like to use Xcode under Mac OS X to compile and run a program written in a language that is not supported, e.g. Fortran. Assuming I have a compiler installed, e.g. gfortran or ifort, what are the steps in the Xcode project settings to make it possible to compile and run the program?
I have created an new, empty project since Fortran is not supported (only C,C++,Objective-C and Swift are selectable in a command line tool application). I created a simple Fortran file. But now I guess I have to add several things to the Builds tab in the project settings to make it compile and run (it works from the command line). What are these steps?
Add an external build system target to your project. External build system targets/projects let you build projects in languages Xcode doesn't natively support. The external build system target/project is in the Other section under OS X on the left side of the assistant. When you click the Next button, you'll be asked for the location of the build tool. Enter the path to your Fortran compiler. When you build the project, Xcode will use the Fortran compiler to do the building.
I am trying to remote debug with FDB over USB and after I've compiled the app with amxmlc, I got the following errors:
No definitions matching so.cuo.platform admob.* could be found
Type was not found or was not a compile-time constant: IntroScreen_mc
...
My app uses admob extension, also in FlashDevelop after I compile the app there are no errors. I am using SDK 4.0 and all my swc libraries have been imported. I think there is something wrong with the paths but I don't know where to look.
Yes ,it a path error.
you not pack the ane lib realy ,you just packed the swc,so it work well when pack,but fail when run application.
how to fix?
right click your project in flash builder ,then set package option of ios or android.check up the check box under package option.
I am trying to run the MvvmCross TipCalc sample. Using NuGet on TipCalc.UI.Droid to resolve references works OK. I then try to do same on TipCalc.Core and get:
Adding 'MvvmCross.PortableSupport 3.0.13' to TipCalc.Core.
Could not install package 'MvvmCross.PortableSupport 3.0.13'. You are trying
to install this package into a project that targets 'portable-win+net40+sl40+wp',
but the package does not contain any assembly references or content files that
are compatible with that framework. For more information, contact the package author.
Shouldn't the project just be ready to go for NuGet and it should "just work"? I am newbie to NuGet and MvvmCross. I am on Win7, VS.NET 2012, NuGet 2.7.40911.225, and latest MvvmCross-Tutorials from GitHub.
The problem will probably be in 'net40' and 'wp' platforms you've included - for PCL reasons we need a minimum of 'net45' and wp75' used - see the chart in http://msdn.microsoft.com/en-us/library/gg597391.aspx for the fact that 'net40' doesn't currently support Mvvm Types (e.g. INotifyPropertyChanged).
If it helps, my current development setup here has remained unchanged since March - it's still http://slodge.blogspot.co.uk/2013/04/my-current-pcl-setup-in-visual-studio.html
Shouldn't the project just be ready to go for NuGet and it should "just work"?
The process towards getting all the tooling for PCLs, nuget, VS, XS, etc working across all the platforms has been slow, hard work.... it is happening and it will one day 'just work' but it continues to take time and lots of work from lots of people.
There are still open workitems within nuget and within Xamarin - e.g. http://nuget.codeplex.com/workitem/2926 - which people are working on; some of the MS legal hurdles have recently been cleared (http://blogs.msdn.com/b/dotnet/archive/2013/10/14/portable-class-library-pcl-now-available-on-all-platforms.aspx); and technically things change on the Xamarin side with almost every Alpha release. But it is hard to get definitive answers on when things will be 100% ready and will "just work".
The good news is that:
with the 2 XML files from http://slodge.blogspot.co.uk/2013/04/my-current-pcl-setup-in-visual-studio.html I and plenty of others have been happily using PCLs and nuget for the last 6 months or so.
progress is still moving forwards
Some of these Q&A's may also help:
MVVMCross StarterPack not installing from Nuget in fresh PCL
Can't install MVVMCross on PCL project
MvvMCross 3.0.6 Nuget package installation issue
Adding MvvmCross nuget package reference to PCL failed
Getting PCL, Mvvmcross, Nuget and Xamarin Studio to play "nice" on Mac
I have recently installed Eclipse Galileo with the PHP Developers Tools. I plan to install the Flash Builder 4 Plug-in to do ActionScript development as well.
I want to use Eclipse to both create an ant build script and execute it to compile ActionScript docs from an ActionScript 3 code library.
The problem is that when I try to run a build.xml file (which every site that answers the ant build questions says it should handle automatically) I never see an option to run it as an Ant Build, not can I find any way to associate XML files to Ant in the Preferences or External Tools dialogs.
I;ve seen numerous tutorials on build Ant build files, but never anything about running the actual build script.
Try to install "Eclipse Java EE Developer Tools" component. It's in "Web, XML, and Java EE Development" of "Galileo - http://download.eclipse.org/releases/galileo" repository.