![]() The spacing between the list items is the same according to a designer on Slack. The Project view actually looses some vertical space, but only because the font size is bigger (Which you can change obviously). "More Whitespace" - The vertical space from the top of the screen to the editor is the exact same. "The toolbar has less icons now" - It's customisable, you can put whatever you want in there. "Monochrome icons" - Only the toolbar icons are monochrome, everything else still uses coloured icons. Breadcrumbs in the Statusbar save some space and look much cleanerĪlso, many of the complaints that I've seen in this thread are either wrong or exaggerated: Showing the git branch next to the title makes it so much easier to understand where I am, when I work with multiple projects and branches. The shaded tool window background nicely separates them from the editor Gutters are now much better at highlighting local changes, while also being less visually obtrusive. Seriously, HN? This is the quality that you reward with hundreds of points? Unlike the author, I happen to have used this UI for the past five months and it solves many of my longstanding gripes with IntelliJ: So that's it, hope it helps if you ran into the same issues I had.> - Rounding of corners. This should now tell CLion to first build and install the binaries into the 'build-debug' folder and then execute the new binary. Make sure 'obs' is still be selected on the leftĪnd then set Exectuable with 'Select other' to. Then click the green play button in the top right corner of the main window or Shift+ F9 to run the selected target.ĭon't worry obs won't run correctly, because it uses the wrong binary, which won't be able to find the obs-data (and even if it does it'll usually report an error about the GPU not being supported).Īfter the compilation is done, you can dismiss the error dialogs from obs and click Edit Configurations. Now you're ready to build obs studio.įirst make sure obs is selected in the top right drop down menu. obs-studio/cmake-build-debug where '.' is the parent folder of the obs-studio repository (Once again this is for the debug profile, for the release profile there's a separate folder). In the next dialog click the plus in the top left corner, and then set name and program to make, arguments to install and the working directory to. in the top right drop-down menu (Note that if you have two profiles you'll have to repeat this step with both and select the correct path). You can also set build options to -j 4 where '4' can be replaced with any number, usually the amount of CPU cores to speed up building.Īfter you click apply CLion will reload the CMake project and you should be able to build and run obs-studio. The path is up to you, if you do want a release profile make sure to set the path to a different one than for debug for obvious reasons. -DCMAKE_INSTALL_PREFIX="$/git/obs-studio/build-debug".if you want a separate release and debug profile), but for this we'll just use the existing debug profile and set the following two options in CMake options: Here you can configure different profiles (eg. ![]() To do this open the settings dialog ( File > Settings or Ctrl + Alt + S) and navigate to Build, Execution, Deployment > CMake. After that you'll have to configure CMake to build a portable version of obs, because the normal build won't find the obs data for some reason. It'll go over it's usual setup routine, but it won't work or otherwise you wouldn't be reading this. ![]() Now you can open the repository folder in CLion.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |