I would like to use an example: I have now downloaded mariadb and compiled it from source and everything works fine.
Let's say, in six months or so, I download the new version and want to build it. How can I find out which options I have set during last build?
Or can I adopt the settings from last build for the new version somehow?
Related
When I start a new project in Comma, it pops up the version I am going to use. Instead of allowing me to select from every version in my rakudobrew list, there's a single option, which is not the one I have selected on the command line. When I run a script, it does not find the modules that are already installed. So how can I
Change the version of Perl 6 it's using for the current project? Or else
How can I install the module it's not finding from Comma IDE?
I can of course get out of comma, change the global Rakudo version, install the module, and then go back to whichever I'm using, but I was wondering how to do that from Comma itself.
To change Perl 6 SDK for the project you go to File -> Project Settings and select project's SDK. Usually it suggests you to choose from not SDKs available from rakudobrew, but one available in your PATH(global, possibly not configured by rakudobrew for this particular shell). So it looks like Perl 6 you have in PATH is not the one that you use from the command line, so the modules are not available.
Clicking on New -> Perl 6 SDK in Project Settings you can manually specify a path to a Perl 6 bin directory you want to have as an SDK, so for rakudobrew you should specify e.g. /home/$user/.rakudobrew/versions/moar-2019.07/install/bin directory. If it will be the same location you have in which perl6 in your command line where you install modules, it should work.
Right now Comma does not do things related to package management, though this feature is planned.
I am trying to get CMake to work with Embarcadero 10.2.3 (Tokyo). I see a some help and blogs. I looks fine (I haven't tried so far), but I get confused about the existing cbproj file that I have. I get the impression that I need a CMake file list (CMakeLists.txt) as well as a cbproj file, if I need to build from the IDE. So in that case, any time I need to add files or settings I need to do in both. Is this true?
Thanks.
I'm looking around in my ~/.gradle folder (relocated to P:\caches\gradle, which doesn't affect this behaviour) and I found some strange folders.
In the past I have updated multiple projects from 2.0 to 2.1 via running gradle wrapper which updated project\gradle\wrapper\gradle-wrapper.properties
I just found out that for some reason the exact same distributionUrl zip file was downloaded multiple times. As you can see they all have the same size and I did a binary diff, they're the same bit by bit except the timestamps:
The contents of each folder above look like this:
I just updated from 2.2 to 2.2.1 and it happened again: this time it's 2 folders not 3. Does anyone know why this happens?
I'm using Gradle from both IntelliJ Idea and the command line.
I made changes to Intellij Community Edition (ce). I can compile and run those changes from within the IntelliJ editor. That launches a second instance of IntelliJ ce which is running from classes containing my changes. What I want to do is just run those changes without having to first load the source, compile and run from within IntelliJ.
Netbeans made this easy by just producing an executable as a result of the build. With Intellij, it's not at all clear what has to be done. I have tried the following-
using the Run configuration Intellij itself uses to run the altered classes- this includes setting the working directory , main class, vm options and classpath. Actually, this doesn't work for reasons unknown to me.
on someone's suggestion, running dist.gant in build. This blows up with very many errors which are not helpful (no class def found errors which indicate some confusion on Intellij's part on classpaths somewhere)
Running WinLauncher.exe under bin gives the error message that it can't find VM options file (although it's in bin, (and also for good measure under bin/win with the other files which are co-located with vmoptions in the intellij directory structure for Intellij proper. )
ALl this is just harder than it should be. The solution is to provide an executable as a result of the build and place it in a predictable location.
Has anyone ever actually DONE what I am trying to do- make changes to the community source then use the resultant editor not as a project you're working with in IntelliJ but as the Intellij editor you're working through?
FOLLOW UP
User60561 had the correct answer. Just to mop up the details, in artifacts, there is a compressed file (win.zip for Windows, mac.zip for Mac etc.). In order to run your snapshot, you have to unzip this archive (after which it will have the same name, minus the zip extension) then go into folder "bin". There you'll see two executables: idea.exe and idea64.exe, for 32 and 64 bit versions, respectively. Clicking on these runs your snapshot.
Adjusting contents of the files idea.exe.vmoptions and idea64.exe.vmoptions lets you set the VM parameters to suit yourself, typically people might want to give the VM more memory through the -Xmx value.
It seems straightforward:
To build the distribution archive of IntelliJ IDEA Community Edition, execute build.xml Ant build script in the root directory of the source code. The results of the build execution can be found at out/artifacts.
https://github.com/JetBrains/intellij-community#building
So download ant, and run ant in the directory that you have it stored in. Make sure to use the commandline to launch ant in order to make sure everything is working correctly.
Initially execute getPlugins.bat/sh, then:
Use update.bat/sh according to it's instructions
Or
Click on: Main Menu | Build | IntelliJ IDEA CE build
Copy content of intellij-community\out\deploy (lib, plugins folder) into existing IJ installation (sometimes it is better to delete existing folders if they contain older dependencies or when the installation was of Ultimate version)
I would like to create a setup project based on WiX which does the following (as well as creating the installation package):
callable from msbuild running on a CI build server (Hudson)
take a version number from some asset in either the setup project or the main assembly
take the current build number from the CI system
create a full product version number [version].[build] such as 1.3.432
store this value in an asset (e.g. the main assembly) is such a way that it can be read out at run time and displayed on the splash window
I have tried a number of approaches and googled a lot but have not found a workable solution. Can anyone help?
The WiX toolset does this by creating a version.cs, a version.h and a version.wxi during the MSBuild then including those files in all the projects. That way our executable can print out their version when you run something like candle.exe -? and all of the bundles and .msi packages have their versions set correctly.
You can see how we do this in tools\WixBuild.Version.targets (here). It would straight forward to override the properties in WixBuild.Version.targets with properties passed via the command-line to MSBuild via Hudson if you wanted.