I'm trying to install Anchor Docking for Lazarus on my Pi
Lazarus v0.9.30.4-6 || Linux raspberrypi 3.12.28 armv6l
At first I used package manager. In the install list, AnchorDocking 0.6 and AnchorDockingDsgn 0.5 always show they will install next time rebuild IDE, but nothing installed although I did rebuild.
So I managed to install manually: packages -> open package files ->
/usr/lib/lazarus/default/examples/anchordocking/anchordocking.lpk
Compile and install, all fine. Now AnchorDocking 6.0 is installed (in the package list)
Next step:
/usr/lib/lazarus/default/examples/anchordocking/design/anchordockingdsgn.lpk
Fatal: can't find unit anchordockingpkg used by lazarus
But when I add anchordockpkg to files list, it's already there, still can't find unit
You don't add the right unit to your use clause. You must add AnchorDocking, eg:
uses
classes, sysutils, AnchorDocking;
Then in the project inspector, click Add, tab New condition and in Package name field type AnchorDocking:
And validate.
Also don't forget to check the example in
\($LazarusSetupDir)\components\anchordocking\minide
which is a working example.
Related
I decided to try out the new unity dots system, or, the new entities package (as well as the hybrid renderer), but I can't find the package in the package manager with preview packages enabled. After looking it up, I could not find any resources, other than one that told me that they moved some of the preview packages out of the package manager, and somewhere else. Does anyone have any idea where it could be?
This is what it looks like on my screen by the way:
From Entity Component System - DOTS Project Setup
Starting with Unity 2020.1, the DOTS packages are not listed in the package manager, even when preview packages are enabled. There are two alternative options to install those packages:
You can use "Add package from git URL..." under the + menu at the top left of the package manager to add packages either by name (such as com.unity.entities), or by git URL (but this option isn't available for DOTS packages). Note that it might take a few moments before the package starts installing.
Alternatively, you can add DOTS packages by directly editing the Packages\manifest.json file in your project. This file requires not only the package name but also a version which can be found by looking at the documentation of each package (such as "com.unity.entities" : "x.x.x-preview.x").
For example currently it would be com.unity.entities" : "0.17.0-preview.41"
And
Follow the link for more information about installing hidden packages.
Maybe also interesting for you:
The recommended set of core packages to be added to a DOTS project is:
com.unity.entities
com.unity.rendering.hybrid
com.unity.dots.editor
I want to learn to use libGDX to create android apps/games.
I used the installer from the libGDX website to create a new project, installed gradle (on windows10) and am able to build/run my project through command line. (tested desktop version and apk via bluestacks, both work nice)
My problem is now, that Netbeans cannot display my code correctly. It says cannot access java.lang at the first line, and things like cannot find symbol, package * does not exist or Override is not an annotation type at the other errors.
I mean, it works somehow, but it's not nice development like that. How can i fix those errors?
I downloaded and installed OpenWrap, since allegedly it was the best way to get binaries for OpenRasta. But when I try to run o add-wrap openrasta-full, OpenWrap gives me this error:
Package openrasta-full not found in repositories.
Just to cover my bases, I also tried o add-wrap openrasta-devtools, since that's the command that's specifically given as an example on the OpenWrap homepage. It just gave me the same error (with the different package name, of course).
When I installed OpenWrap (o.exe) from openwrap.org, and ran it the first time, I got a console window asking if I wanted to install, and I chose the "install and add to the path" option. It chugged for several minutes, downloading packages, but then the console window closed, so I don't know if the "install" completed successfully. Now when I try to re-run the file I downloaded, I just get an error: "The term 'o' is not a recognized command or alias. Check the spelling or enter 'get-help' to get a list of available commands." So apparently it's the same EXE and self-installs, so I have no way to re-run the install or even tell whether it was successful.
How can I troubleshoot this and get OpenRasta installed?
So there was some issues with the 2.1 packages that all should have been resolved now.
To create an OpenRasta site you can:
OpenWrap 1.0
With 1.0, you need to first create a new project
c:\src> o init-wrap myProject
c:\src> cd myProject
Then create a new asp.net site (or console app or whatever you want). You then need to hook up OpenWrap to your project.
c:\src\myProject> o init-wrap -all
And finally add the OpenRasta packages to your project.
c:\src\myProject> o add-wrap openrasta-full
OpenWrap 2.0
If you're using OpenWrap 2.0, it's a bit easier.
First, install the devtools on your system.
c:\src> o add-wrap openrasta-devtools -system
Then initialize a new project
c:\src> o init-wrap myProject
c:\src> cd myProject
And create a new OpenRasta site using
c:\src\myProject> o new-OpenRastaSite mySolutionName My.Base.Namespace
This will use the default templates to create an OpenRasta site.
As OpenWrap 2.0 gets more functionality around templating, I'll probably make the openwrap creation implicit (if you're not within an OpenWrap project, the templates will create one) and more options available in the template (hosting type for example).
I have started to try to use StatET and Texlipse with a view to producing SWEAVE reports. When starting the R console in the StatET plug-in for Eclipse (OS X 10.6.4), I get the message:
[INFO] The R package 'rj' is not available, R-StatET tools cannot be initialized.
Information on http://www.walware.de/goto/statet states:
"The package only works in the default R Console (RJ) in StatET. Therefore you have to install and update it using the command line":
R CMD INSTALL --no-test-load rj_*.tar.gz
What does this mean exactly?
In Eclipse under "Install new Software" and the site
WalWare - http://download.walware.de/eclipse-3.6
it states that
RJ Core Library 0.5.0.b201008271600sw
is already installed.
Any helpful guidance gratefully received.
[rant] I also lack the reputation to put my response where it belongs. And there's no button there indicating this. Just a big screen full of nowhere desired to click upon. Negative discoverability sucks. It sucks in Eclipse and it sucks here, too. [/rant]
I'm finding rj frustrating under Ubuntu. On my system, with each major Ubuntu upgrade with a new version of R, I have to go through this procedure over again.
One time I tried to use a tilde (~) character in a path name within some Eclipse configuration field. This failed silently.
My current configuration is as follows. In my ~/.Renviron file:
R_LIBS_USER=~/etc/R/amd64/2.11
Once rJava works, there is an rJava directory here. Just so I don't drive myself insane, in ~/etc/R/README I put a note that my current R configuration is controlled by ~/.Renviron
Somehow at one point I ended up with permission problems where
R CMD javareconf
was failing. Once in frustration I foolishly ran this under sudo to work around this problem, and ended up with permission problems on the generated files. Stupid! The correct fix was to make all the files in /etc/R world readable. Maybe javareconf is only important if you mess with your default Java. Previously, I was running the Sun's JRE. Since 10.10 I'm running icedtea6 and it seems to be working OK. One time it was just the thing to make my configuration work again.
Once I have the right Java binding, from command line R:
install.packages("rJava")
I've had file permission problems running this in the past. I think it was fixed by making all files in /etc/R world readable.
The following is a useful diagnostic to see if this worked, from within any R console:
> system.file("jri",package="rJava")
[1] "/home/allan/etc/R/amd64/2.11/rJava/jri"
If it doesn't look right under Eclipse, there is also some startup debugging available, though it took forever before I noticed this in the docs at StatET.
I created an R Console run configuration for R 2.11 debug In the JRE tab add -Dde.walware.rj.verbose=true. In the Common tab, click Allocate additional Error Log Consoles.
The main configuration options are as follows. Main tab, Launch Type: RJ. R_Config tab, you need to select a Configured R Installation, or create/edit one if you don't have one that works. Mine is Name=R, Location=/usr/lib64/R In the Environment tab I have R_LIBS_USER=/home/USER/etc/R/amd64/2.11 according to how I set things up above. Do not use the tilde (~) character here!
If you end up mucking about with this problem as much as I did, you end up killing a lot of dead consoles. In the Main tab I added the program option --no-save. I don't think this does anything, since I can't end my console by pressing CTRL-D. In the R_Console tab, I added the following R snippet:
q <- function(save = "no", status = 0, runLast = TRUE){
.Internal(quit(save, status, runLast))
#<environment: namespace:base>
}
This gets rid of the annoying "save workspace" prompt when killing an R console with the red square (is that symbolic?) My current workspace also includes a C project, so my R console constantly comes up underneath a blank C-Build console. Annoying as all hell! Haven't solved that yet, but I did discover that from within a StatET code windows the keybinding CTRL-R C pulls the R console to the top.
With my R 2.11 debug configuration I get an extra console titled /usr/lib/jvm/java-6-openjdk/bin/java. You'll have to spelunk the console drop-down to find it. The following is a pertinent snippet of a successful initialization:
CONFIG: JR library path:
/home/allan/etc/R/amd64/2.11
/usr/local/lib64/R/site-library
/usr/lib64/R/library
10-Dec-2010 7:56:47 AM org.rosuda.rj.JRClassLoader addClassPath
FINE: Added '/home/allan/etc/R/amd64/2.11/rJava/java' to classpath of URL loader
A lot more spoo, then finally:
10-Dec-2010 7:56:48 AM de.walware.rj.server.jriImpl.RosudaJRIServer start
INFO: R engine started successfully. New Client-State: 'Connected'.
Looks good, right? But lo and behold in the R console:
[INFO] The R package 'rj' is not available, R-StatET tools cannot be initialized.
Ignore the lying bastard! Turns out my rj is working just fine. No idea why this failure message persists.
Every time around the block with this problem some new amazing piece of gravel ends up in my sneaker.
I don't know whether I've covered everything, but I've written enough for now. Maybe if there are comments I'll come back and fill in the blanks.
Note: found an Eclipse plugin for console switching by keyboard here: Eclipse: Keyboard shortcut for switching between consoles?
It looks like you need to install the RJ library which can be downloaded from the StatET site here: http://download.walware.de/rj/rj_0.5.0-5.tar.gz (more recent versions of RJ can be found at http://www.walware.de/it/downloads/rj.mframe)
If you save that file on your desktop, you can then load it into R with the command they provided R CMD INSTALL --no-test-load rj_*.tar.gz after navigating to your desktop or wherever you saved the library file. Alternatively, you MAY be able to use the GUI interface and select Install packages from local ZIP files under Packages in R, though I haven't used R on a Mac so the layout may be slightly different.
After installing rj with in the R console using
install.packages(c("rj", "rj.gd"), repos="http://download.walware.de/rj-1.1")
(See http://www.walware.de/?page=/it/statet/troubleshooting.mframe for the correct rj version),
do not forget to update the R_LIBS variable in Eclipse (Windows -> Preferences -> StatET -> Run/Debug -> R Environments -> Edit). To find out the value just type in the R console:
packageDescription("rj").
In my windows 8 installation this returns C:/Users/Fibonacci.PYTHAGORAS/Documents/R/win-library/3.0/rj/Meta/package.rds. The value of R_LIBS I set to
C:/Users/Fibonacci.PYTHAGORAS/Documents/R/win-library/3.0
which is the path where all libraries are installed.
As stated in http://www.walware.de/?page=/it/statet/troubleshooting.mframe newer versions (Versions > 0.5.5) do not need the R CMD INSTALL etc... command.
Here the quite similar I had and the solution I found.
I originally installed Statet using the Eclipse built-in tool "Install new software ...."
I seems it downloaded Statet + rj and that the installation process went well.
After this first installation, I tried to install both packages again. Eclipse refused reading that they already are installed. And, both packages/programs were actually listed in the window of Eclipse.
But, the R console still refused to launch, the dialog box reading that I had to check whether rj was available and that the file paths were correct. Another strange thing was that window explorer had been unable to locate rj on my disk.
???
To solve my whole problem, I simply downloaded rj from http://www.walware.de/ and installed this package via the r console and using the basic install.packages() command.
It now works perfectly .
But, I still don't understand everything ..... :-)
I'd make a comment but I lack the necessary reputation. For Windows, the procedure is the same. There's no zip file. Use the tar.gz. Worked for me. The command, working from the same folder as the downloaded file:
$ G:\R-2.12.0\bin\i386\R.exe CMD INSTALL --no-test-load rj_*.tar.gz
The project is now hosted on GitLab, see
https://gitlab.com/walware/de.walware.rj-server.gr/-/wikis/Installation.
To install:
install.packages(c("rj", "rj.gd"), repos="https://download.walware.de/rj-4.0")
Note that binary packages are available for Windows.
As explained in this message from Stephan Wahlbrink on 2022-02-03 announcing StatET 4.5 release, this version works with R 3.6 to 4.1, and RJ-4.0.
For current information on StatET, check the home page and especially the news.
I have a deployment project which will not let me install over an older version. The msi file says to uninstall the program first from Add/Remove programs. This is not a good user experience. How can I do it so that the installer will simply remove the software first and then install the new version?
This is tricky, you have to do following steps,
Set Remove Previous Installation as True
Set Detect new version as True
Your C# program's version must increase with every deployment
You should change version of your installer to one higher version and it will ask you to change product code, select YES.
Do not change your upgrade code, let it be same.
If you do not do 3rd step correctly, installer will still install and keep the old file, your file version of every file must be new if you have changed your content.
I tried out a few scenarios, maybe this will help someone save some time
If Assembly Version changes AND project installer version changes (with ProductCode Guid changing also)
-> App installs over the top of existing one
-> dlls and exe versions get updated
-> IF path installed to is different, existing initially installed project files are deleted from where they were installed. (and files made since remain)
If Assembly Version changes AND project installer version changes (without ProductCode Guid changing)
-> User is asked to manually remove the application
-> if they go ahead and remove from control panel first, app can then be installed and the dlls and exes get updated to the new version
If ONLY Assembly Version changes, or only project installer version changes (without ProductCode Guid changing)
-> User is asked to manually remove the application
-> if they go ahead and remove from control panel first, app can then be installed and the dlls and exes get updated to the new version
If ONLY project installer version changes (with ProductCode Guid changing also)
-> MSI goes through install process, but dlls and exe do not change version -they are as per assembly version, and are replaced with files of same assembly build version
-> IF path installed to is different, existing initially installed project files are deleted from where they were installed. (any files made since remain)
If project installer version changes (with ProductCode Guid changing also) and assembly version is lower than installed version
-> Installation will commence, at the end user is informed install fails as old version.
Set setup project property RemovePreviousVersions True
But you have to use same UpgradeCode in both setup applications
You can do this sometimes after installing new version the old product will remain same.
You need to change the sequence number of RemoveExistingProducts ,It must schedule between
Install Validate action and InstallInitialize . You can do this by ORCA
For Ex InstallValidate=1400
InstallInitialize =1500
Then RemoveExistingProducts =1450
If you are using visual studio 2012 or upper version ,
If you have already installer folder under the solution folder, just open the Project assistant under Installer and double click on it .
2.Once you open Project assistant you see the Application Information ,here you can enter the version you want to change it.