How to compile Ctrlr or CtrlrX 5.6 versions in Visual Studio 2022

[dnaldoog]

These are basic instructions for compiling a Release version of CtrlrX

The same procedure applies to the Debug option in Visual Studio

This procedure is for Windows 11 - I am guessing the same for WIndows 10

Download CtrlrX Source Code

METHOD 1 (GUI based but harder)

(1) Download GitHib Desktop and install

(2) In GitHib Desktop
File -> Clone repository -> url type https://github.com/damiensellier/CtrlrX

(3) Choose C:\Users\%USERNAME%\Documents\CtrlrX\ *or another directory of your choosing
This is where all the source code is written to.
This clone of the repository defaults to the master branch, but you can choose different commits in the "Current Branch" tab

(4) Change into directory: C:\Users\%USERNAME%\Documents\CtrlrX\Source\Misc\boost

(5) Unzip the file to ./boost/boost/boost_content.

METHOD 2 (easier)

(1) Download Git for Windows

(2) In PowerShell

cd C:\Users\$env:username\Documents\
git clone https://github.com/damiensellier/CtrlrX
cd .\CtrlrX\Source\Misc\boost\
tar -xvf .\boost.zip
cd ../../../

‡ Note on building a different branch:

Here, as an example, I want to build the latest branch 5.6.34-Maintenance.
Open PowerShell:

cd C:\Users\$env:username\Documents\CtrlrX
git checkout --track origin/5.6.34-Maintenance

---

VST2 Support & Build Instructions

Important Note: VST2 Discontinuation and SDK Availability

We strongly recommend that users transition to building the VST3 version of CtrlrX instead of VST2, as VST3 is the current and actively supported standard.

Steinberg officially discontinued the VST2 API and SDK in January 2022. As a result, the VST2 SDK is no longer publicly available for download or new licensing. This means that for most new users, building a VST2.4 plugin directly from this project will not be possible without prior access to the SDK. For more information, please refer to Steinberg's official announcement: VST 2 Discontinued.

However, if you are an existing licensee of the VST2 SDK (meaning you had access to it prior to its discontinuation), you can still compile a VST2 version of CtrlrX. Your ability to build and distribute this VST2.4 version of the plugin will be governed solely by the terms of your specific VST2 SDK license agreement with Steinberg.

‡ How to point Projucer to the vst2 SDK path.

(1) Download VST2 SDK zip file

(2) Extract folder pluginterfaces

(3) Move to folder to CtrlrX->Source->Plugin

(4) Open Projucer

(5) Set VST (Legacy Path) SDK to VST2 SDK folder in step (3) CtrlrX->Source->Plugin

---

Download Projucer

(1) Download juce-6.1.3-windows.zip from JUCE 6.1.3 and unzip:

(2) Open the Zipped download and click on the JUCE folder and extract the file Projucer.exe to your preferred folder:

---

Open Projucer

(1) From within projucer, navigate to the jucer file in the CtrlrX folder ( C:\Users\%USERNAME%\Documents\CtrlrX)

Choose the file CtrlrX 5.6.34 [Without AAX].jucer

(2) Click File -> Global paths and set the following paths:

• Path to JUCE: C:\Users\%USERNAME%\Documents\CtrlrX\JUCE
• JUCE Modules: C:\Users\%USERNAME%\Documents\CtrlrX\JUCE\modules

(3) Click on the Selected Exporter window

(4) Select Visual Studio 2022 and click the Visual Studio icon. Visual Studio 2022 should automatically open.

(5) Close Projucer

---

Compiling CtrlrX

In Visual Studio, if you receive a prompt to retarget Projects:
Select Upgrade to v143

‡ Note: You shouldn't have to do this if you chose VS 2022 as selected exporter in projucer.

(1) There are two dropdown menus at the top of the menu.
Choose Release x64

(2) Now we can try to build CtrlrX.

• Click on Build Solution <or>
• You can build individual builds by right clicking on them in Solution Explorer and clicking build <or>
• Ctrl-B after left clicking on a solution in Solution Explorer .
• <or> F5 to start debugging.

• CtrlrX_SharedCode
• CtrlrX_StandalonePlugin
• CtrlrX_VST
• CtrlrX_VST3

If you chose Release, you will find the newly built executable, VST and VST3 files in:
C:\Users\%USERNAME%\Documents\CtrlrX\Builds\VisualStudio2022\x64\Release\Standalone Plugin

If you get a "The program can't start because MSVCP140.dll is missing .." error:
Install the Latest Microsoft Visual C++ Redistributable Version for either x86 or x64:

https://aka.ms/vs/17/release/vc_redist.x86.exe
https://aka.ms/vs/17/release/vc_redist.x64.exe

You should be able to now run your own compiled version of CtrlrX.

Build CtrlX on Windows.pdf

[dobo365]

Thx for documenting this. Will be useful when I'll switch to VS2022.
I'm still using VS2019 and the guide from bijlevel.
There the boost files are at Source/Misc/boost/boost. You indicate to have them one folder upper. Sure?
I just compiled the latest 5.6.32 on my PC with VS2019 and I had to have boost/boost.
Seems also not anymore needed to do the remove finals. Good!

[dnaldoog]

Thank you

I remember previously doing boost/ boost too but I haven’t tried that on VS2022. It probably works too, so I don’t think one has to do it just with boost folder. Might try later.

Must be that as long as boost folder is present in source/misc (is it?), the compiler can locate boost files even if in a sub directory.

To me it seemed neater that’s all, but probably either way is fine.

[damiensellier]

I'll update the WIKI page about the compilation guides with your PDF. Thanks!

In Windows 10, boost needs to be unzipped in the folder so that the path to files is : /boost/boost/boost_content
Thanks John!

[dnaldoog]

Oh I see - I'll just change it to that seeing as either works in Win11!

I want to keep it simple so I won't mention this

[damiensellier]

I was also wondering if it was still required to do the cygwin64 thing from the terminal on WIN11 ?

[dnaldoog]

What is that? I think it’s in bijlevel’s guide, right?

But whenever I followed his guide I ignored that. On Windows 11 and VS2022 the process is now, dare I say, easy - but perhaps there’s a gotcha in the way I compile?

[dnaldoog]

Note: On a fresh install of Windows 11, whether using the installer or just the executable standalone, CtrlrX did not load. Neither were there any error messages. Just totally unresponsive.

To fix this I needed to install:

• https://aka.ms/vs/17/release/vc_redist.x64.exe

Now it loads fine.

[dobo365]

FYI, last week I built and compiled Ctrlx 5.6.32 on both Windows 10 and Windows 11 and it was straightforward.
The only need was to unzip boost.zip and have the content in boost/boost
Remove finals and the Cygwin manipulation was not needed.
I used Juce 6.1.5 and Visual Studio 2019.

And I also started making a cleaner documentation of the build in my Ctrlr guide. Will complete it with some points you mentioned above.
Will chat with bijlevel to get the Mac M1 version with Xcode because no success there...

[dnaldoog]

Excellent - well I just changed the VS2022 instructions above to unzip to boost/boost as both work.

[dnaldoog]

Hi Damien,

It looks like with the latest 5.6.34-Maintenance that in order to compile successfully on Windows, I need to uncheck AAX and possibly AU in this setting on the Projucer.

Compiling fails otherwise.

Does that seem about right to you? If so, I'll update the instructions for compiling here.

[damiensellier]

Yes it's ok, it's because projucer is looking for the aax SDK, without result.
I added another projucer project file without aax and vst2 in the root of 5.6.34 :

https://github.com/damiensellier/CtrlrX/blob/5.6.34-Maintenance/CtrlrX%205.6.34%20%5BWithout%20AAX%20%26%20VST%5D.jucer

Edit : without aax and vst2 indeed :)

[damiensellier]

There's also a projucer file just without the aax plugin as well : https://github.com/damiensellier/CtrlrX/blob/5.6.34-Maintenance/CtrlrX%205.6.34%20%5BWithout%20AAX%5D.jucer

I did 3 version for the GitHub actions to compile online. Not sure which one of them I'll be keeping for the official release.

[dnaldoog]

Thank you. I updated the how to on this page.

[dobo365]

Updated to latest 5.6.34 Maintenance.
Downloaded VS2022 and got the prompt shown above to re-target Projects.
Modified properties as usual.
During build, got a lot of "Unknown compiler version - please run the configure tests and report the results" messages.
Looking on stackoverflow it seems a boost version issue.
Busy to download boost 1.88. Will replace the boost we have in CtrlrX and try building.

We have boost 1.57 and it is 15.7MB
Boost 1.88 is 235 MB... Takes 15 min to unzip...
Is our current boost just an extract of the full boost?

Any comment / idea?

[dobo365]

It was at the right place.
The boost 1.88 zip files contains more than just the boost folder.
I have now kept only the boost folder which is 135MB.

Now getting MANY other messages: message : The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use <boost/bind/bind.hpp> + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.

But OK, build of SharedCode succeeded.
Don't know where to type that "define BOOST_BIND_GLOBAL_PLACEHOLDERS"...
Shall I revert to VS2019? Is it even possible?

Build of Standalone OK.
Quickly tested. Mode V3 Legacy shows the Ctrlr popup nicely!!!
Properties a bit too dark but I'll adapt that.
Need to test further but seems promising.

[dobo365]

I'll try with some previous version of boost.
I'll also search where to put define BOOST_BIND_GLOBAL_PLACEHOLDERS so we can keep using the last version of boost.

[damiensellier]

Try adding "BOOST_BIND_GLOBAL_PLACEHOLDERS=1" in projucer in the Preprocessor Definitions" or "Extra Compiler Flags" , save your projucer project and start VS from the icon top right.. as usual.

[damiensellier]

use a space inbetween both declarations :

[damiensellier]

I just updated boost with 1.88.0 from https://github.com/boostorg/boost/releases/download/boost-1.88.0/boost-1.88.0-b2-nodocs.zip (b2 for binaries, no extra documentations or source files).
And added the preprocessor MACRO in projucer and it's ok.
I personnally don't need it but if it makes the process easier to everyone else, I can push the update for 5.6.34.

Let me know how it went on Windows ;)

A bientôt

[dnaldoog]

Here's how to compile CtrlrX in Windows PowerShell up to the point where you open projucer, including how to build a specific branch.
In this case 5.6.34-Maintenance.

Note that in this example the working directory is in Documents.

cd C:\Users\$env:username\Documents\CtrlrX
git clone https://github.com/damiensellier/CtrlrX
cd .\Source\Misc\boost\
tar -xf .\boost.zip
cd ../../../
git checkout --track origin/5.6.34-Maintenance

• Now open projucer and proceed with guide above for compiling:

[damiensellier]

Could you please add an exporter for VS2022 in Projucer, I don't have it on my Windows setup and I can't add it on macOS.

On your Windows machine (with VS2022 installed):

1. Open the Projucer application.
2. Open your existing .jucer project file. (CtrlrX 5.6.34.jucer)
3. Now, in the Projucer, navigate to the "Exporters" section on the left sidebar.
4. Click the "+" button at the bottom of the "Exporters" list.
5. In the "Add Exporter" dialog, you should now see "Visual Studio 2022" as an option (assuming Projucer correctly detected your VS2022 installation). Select it.
6. Projucer will then add a new Visual Studio 2022 exporter to your project.
7. You can then select this new VS2022 exporter and go through its settings to adjust them as needed (e.g., target architecture like x64, debug/release configurations, etc.). Just copy them from the VS2019 settings.
8. Once you've configured it, save your .jucer file. This will generate the .sln and .vcxproj files for Visual Studio 2022 in your project's Builds folder on your Windows machine.
9. You can then open the generated .sln file in Visual Studio 2022 and build your project.

Please post the .jucer file here and I'll check the custom settings and will push it to the github repo with the 3 variants (no AAX etc)

Thanks!

[damiensellier]

I'll probably add the AAX SDK to the Misc/ folder since the version 2.8.1 is now under GPL v3 which allows the distribution of the SDK under this type of licensing. (It's now included straight away in JUCE 8 like VST3 and AU..)
That will remove some confusion and the AAX SDK will point to the CtrlrX related content.

[dnaldoog]

Do you want the WIN32 configs (debug & release)? I'm doing the configs right now.

That would be great!

I updated the how to at the top of the page. May have to adjust when the dust settles around which projucer files will be included.

I personally don't mind just just going in and disabling AAX manually.

[damiensellier]

The link to the juicer project updated without aax is just above:
https://github.com/user-attachments/files/21009115/CtrlrX.5.6.34.Without.AAX.jucer.zip

[damiensellier]

If it's confirmed working on windows with vs2022 and boost 1.8 I'll push the updated files tonight.

[dnaldoog]

Yes confirmed as working:

[dnaldoog]

Yes confirmed as working:

Actually no - it is not working but I was able to compile using VS2019 in projucer, disabling AAX and including Boost 1.88 libraries manually extracted into Source\Misc\boost\boost

I think the projucer as VS2022 doesn't prompt me to retarget solution to 1.43

When opening in projucer through VS2022 I get this error:

BOOST version.cpp

[damiensellier]

Did you have the new macro in the preprocessor box? :
JUCE_USE_CUSTOM_PLUGIN_STANDALONE_APP=1 BOOST_BIND_GLOBAL_PLACEHOLDERS=1

also the build folder is supposed to go there :Builds/VisualStudio2022

SO there's no need to retarget the destination folder for the compilation.

and you can select the toolkit version for vs2022 it is 1.43 but for vs2019 it was 1.42 maybe it's going to work.

I recommend you wipe off the build folder to start from scratch it will be recreated with the projucer if you launch VS2022 from the top right icon.

[damiensellier]

NOTE: the file you posted at first was missing a lot of options, please use mine :
CtrlrX 5.6.34 [Without AAX].jucer.zip

[damiensellier]

EDITED jucer file, the app icons were not the right one...

[dnaldoog]

Did you have the new macro in the preprocessor box? : JUCE_USE_CUSTOM_PLUGIN_STANDALONE_APP=1 BOOST_BIND_GLOBAL_PLACEHOLDERS=1

Yes I have that in the latest file CtrlrX 5.6.34 [Without AAX].jucer.zip

I recommend you wipe off the build folder to start from scratch it will be recreated with the projucer if you launch VS2022 from the top right icon.

Deleting the Builds Folder seems to have fixed it!

Compiled with boost 1.88

[damiensellier]

Excellent I updated everything on the 5.6.34 branch
Thanks for your help!

[dnaldoog]

This is code for displaying information about Lua,JUCE and Boost - maybe looks a bit messy but thought I would include the code in case you want to use it.

CtrlrAbout.zip

[damiensellier]

Thanks, I remember those macros were used in the old ctrlr version. I removed them for clarity, but you're right I'll add them back under the release line.

[dnaldoog]

Hi Damien,

Here is the projucer file with VS2022 added as exporter:

CtrlrX 5.6.34 [Without AAX].zip

[damiensellier]

https://github.com/damiensellier/CtrlrX/blob/5.6.34-Maintenance/CtrlrX%205.6.34%20%5BWithout%20AAX%5D.jucer
https://github.com/damiensellier/CtrlrX/blob/5.6.34-Maintenance/CtrlrX%205.6.34.jucer

I removed the .jucer without VST2 since the project is pointing to the sdk inside ctrlr so it won't return any error on compilation.
I'll check with the people at Avid for AAX to confirm I can distribute their SDK 2.8.1 under GPL v3 and will add it inside the Misc/ folder as well so that we have a single jucer file covering everyone's need.

[dnaldoog]

This is a screen shot of the exporters area of the file I sent. Did I do something wrong?

Actually AAX was still enabled!

This is the File menu - the save as button is greyed out - so it just saves back to the CtrlrX build folder.

Here is is again without AAX

CtrlrX 5.6.34 [Without AAX].jucer.zip

[damiensellier]

This is your actual Visual Studio 2022 main settings :

VST2 legacy path to sdk is missing and the preprocessor is missing too and extra compiler flag is also empty and your icons are not selected to ctrlr_logo.png

This is what you should have if VS2019 was working great...

Picture of the current file at : https://github.com/damiensellier/CtrlrX/blob/5.6.34-Maintenance/CtrlrX%205.6.34%20%5BWithout%20AAX%5D.jucer

[damiensellier]

I would recommend you use mine :) It's going to work for sure.

[damiensellier]

I just pushed the About window update showing the library versions infos :
damiensellier#117

[dnaldoog]

I think I'm a bit confused. I thought you needed me to create the file for you in Windows. But that's okay - I downloaded your version directly from GitHub and it compiles!

[damiensellier]

Oh sorry, I just needed you to create the first file so that VS2022 shows up in the list. Once done, I set everything as it should.
Everything is now up to date on the 5.6.34 branch even the new About window with the lib details :

[dnaldoog]

Just did a clean reinstall and building. For VS2022 the retarget SDK window doesn't popup in Visual Studio. Makes sense, so I will change the instructions above. Excellent stuff!

[dnaldoog]

Here it is but with boost 1.57? You got luabind in there too! I was wondering about that.

String luabindVersion = _STR(LUABIND_VERSION / 1000) + "." + _STR(LUABIND_VERSION / 100 % 100) + "." + _STR(LUABIND_VERSION % 100);

[damiensellier]

You need to update your boost folder, I replaced the boost zip in the repository. It's 1.8.8. we're almost there!

[dnaldoog]

I deleted my CtrlrX folder (containing boost in cd .\CtrlrX\Source\Misc\boost\ - which was actually 1.8.8) and recloned and changed to the branch with:

cd C:\Users\$env:username\Documents\CtrlrX
git checkout --track origin/5.6.34-Maintenance

Maybe that doesn't update the boost folder? Anyway, that will be fixed when the branch 5.6.34-Maintenance is merged with master, right?

[damiensellier]

You would need to add something about how to point projucer to the vst2 SDK path.

Navigate to "File" > "Global Paths..." (or sometimes just "Settings" via the gear icon).
In the Global Paths window, locate the entry specifically for "VST (Legacy) SDK".
Set this path to the root directory where your VST2 SDK is located (e.g., the folder containing the pluginterfaces directory and other VST2 SDK components). This path is critical for JUCE to find the necessary VST2 headers and libraries.

[dnaldoog]

You would need to add something about how to point projucer to the vst2 SDK path.

Navigate to "File" > "Global Paths..." (or sometimes just "Settings" via the gear icon). In the Global Paths window, locate the entry specifically for "VST (Legacy) SDK". Set this path to the root directory where your VST2 SDK is located (e.g., the folder containing the pluginterfaces directory and other VST2 SDK components). This path is critical for JUCE to find the necessary VST2 headers and libraries.

Okay, changed it. Is it okay?

[damiensellier]

All good 👍

[dobo365]

As I said... You are great, guys!
Sorry, didn't touch anything related to Ctrlr the whole week.
Pain to my back and lot's of work. So, just wanted to be relax in the evening.
Hope to look at this during the w-e.
Indeed, Projucer was still launching VS2019 but once I got the jucer file, I closed Projucer then opened the jucer file in VS2022 manually and built from there ;-)
But now with all the changes you did I can start from a more up to date setup with everything :)

[dnaldoog]

As I said... You are great, guys! Sorry, didn't touch anything related to Ctrlr the whole week. Pain to my back and lot's of work. So, just wanted to be relax in the evening. Hope to look at this during the w-e. Indeed, Projucer was still launching VS2019 but once I got the jucer file, I closed Projucer then opened the jucer file in VS2022 manually and built from there ;-) But now with all the changes you did I can start from a more up to date setup with everything :)

That's great to hear!

[dobo365]

Some feedback:

• building 5.6.34 is working fine in Windows! I already had Projucer 6.1.5. After installing VS2022, I got the choice VS2019 or VS2022 in Projucer. Selecting VS2022 was starting 2019... In fact was depending on the association of .sln files with VS2019. Just changed that and it is OK
• been doing many changes and still busy trying things. I'll provide it to you (I'm in holidays from next week so will have more time

Already OK:

• rename method (only in the tree, not in the code because you can have any function in a "method")
• force all text properties to have white background and black text for better readability
• force resizer to always be yellow
• height between methods set to 24 io 32
• method size text in italic
• light red buttons for closing panels
• changes to remove some warnings

Added a v4 Classic theme but the colors are not at all the ones specified. Need to understand why.
Identified a few issues but will retry all to be sure

Next to look at:

• standalone, VST2, VST3 export, test and check look and feel
• light purple methods on mouse over. Look at CtrlrValueTreeEditorItem in CtrlrValueTreeEditor.h
  Add void itemMouseOver (const MouseEvent &e) check itemClicked to do similar

• ctrlrMethodEditor.cpp itemClicked -> itemMouseOver

• use tree full width instead of item width CtrlrValueTreeEditorItem::getItemWidth () in CtrlrValueTreeEditor.cpp
• underline property label on mouse over (need to understand why not working). Display of popup with explanation (from xml file) on click
• find stripped background as in 5.3.201 and find if better or not
• understand why colors of Classic V4 are not the ones specified
• (minor) panel canvas in white by default
• need to add a border / black outline in Lua editor - Column method, in order to get some "3D" effect as panel properties. Or add outline to the resizer to see it when it is grey?

Missing nil attribute in replaceText() / appendText() is making CtrlrX crash (I have it in ReadStateData and in many places)
So must update all my panels and save them in a new version.

Trying to find in 5.3 (build d0d40b5 february 2016) how the stripped background was done. Still not found.

Again, thx a lot guys for your improvements and I hope my small contributions are also adding some value to you.

[dobo365]

I'm not an expert of pull and push requests.
I'm doing changes locally on my PC then my plan was to push it to my own version of of CtrlrX on github.
I still don't know what will happen with boost folder as I don't want to push all separated files.

What I agreed with Damien is to create an Issue on CtrlrX for each topic so he can then take them one by one and implement them on his side. Probably not the best shared code development technique BUT at least we have all changes documented as an issue with explanatory text.

But for sure, Github can cope with several people working on the code. Basically you are only sending what you changed but this is not actually implemented. Damien has to select what he wants to take.

Yep, please do the change and give the code.
It should be done for both Ctrl-F and bottom tab.
I thought to add a checkbox with a text like "Keep methods opened after a match"
A bit long but I would have put it just under the existing Match case. Like:

Fun, isn't it?

I'm busy to make a personnalized Wiki sidebar containing the current content but in a better structured way.

I don't know what you think but I think we should probably drop writing here in Ctrlr because it is abandonware and we can only do changes in CtrlrX. I have mixed feelings but I feel it is less and less logical to continue here...

[dobo365]

Actually, another thing is that the bottom menu search and replace doesn’t work on closed files, so probably we can incorporate the same functionality as found in the find menu, which now searches closed files, on the top right of the editor.

It works but the code is not exactly the same. Please look in the coded I posted above and change the indicated files.
I also posted it at: damiensellier#118

[dnaldoog]

I'll add that checkbox there as well as the Ctrl+F dialog and maybe even in the menu.

[dnaldoog]

Actually, another thing is that the bottom menu search and replace doesn’t work on closed files, so probably we can incorporate the same functionality as found in the find menu, which now searches closed files, on the top right of the editor.

It works but the code is not exactly the same. Please look in the coded I posted above and change the indicated files. I also posted it at: damiensellier#118

So now the code I added for the top search doesn't open files and the bottom search always opens files.

---

On the top we also have the option to find all closed files but not open so I might add a checkbox in the top left menu to toggle that option in both searches,

But I was thinking of search & replace on closed files but that could be dangerous. At the moment only open files can have search and replace and I think it should stay that way.

[dnaldoog]

Actually, another thing is that the bottom menu search and replace doesn’t work on closed files, so probably we can incorporate the same functionality as found in the find menu, which now searches closed files, on the top right of the editor.

It works but the code is not exactly the same. Please look in the coded I posted above and change the indicated files. I also posted it at: damiensellier#118

Here is a compiled standalone for you to check:

CtrlrX_7212025.zip

[dnaldoog]

I agree that we should wean off Ctrlr as CtrlrX really gains momentum.

Go to Damien's github and click here:

This will create a fork of master on your GitHub.

In a directory on your pc copy and paste this whole command:

cd C:\Users\$env:username\Documents\
git clone https://github.com/damiensellier/CtrlrX
cd .\CtrlrX\Source\Misc\boost\
tar -xf .\boost.zip
cd ../../../

You'll probably want to work on the latest branch unless that branch gets merged into master:

cd C:\Users\$env:username\Documents\CtrlrX
git checkout --track origin/5.6.34-Maintenance
git fetch

Now you have the latest branch on your pc.

After working on some code, you might want to do a Pull Request for Damien to look at.

At the moment your remote branch is pointing to Damien's repository https://github.com/damiensellier/CtrlrX.

The trick is to upload to your github fork, so you need to remove reference to origin pointing to Damien's github:

git remote rm origin
git remote add origin https://github.com/dobo365/CtrlrX.git

Now your remote points to your fork:

 git remote -v

To make changes to the code, create a new branch:

git checkout -b mynewcode

This should create a new branch containing all the code from the branch you downloaded with
git checkout --track origin/5.6.34-Maintenance

When you are happy with code changes

git add .

then commit with a message

git commit -m "New changes to search menu"

Now we upload (push) to GitHub

git push -u origin mynewcode

If you now go to your GitHub, you should see a message prompting you to perform a PULL REQUEST
Click on that link. Fill in the form and submt and those changes (Pull Request) will be sent to Damien.

---

It is true that I sometimes have trouble with git wanting to push big files, but I have never had it try to push the boost folder.

Attached is my .gitignore file put at the top level of your CtrlrX folder.
I only learnt recently that for it to work, you need to add it to your project. That had me confused as to why the /Builds folder was always being added

git add .gitignore

.gitignore.zip

[dobo365]

Cool.
FYI, I also added
owner.getMethodEditArea()->insertOutput("\nSearch done\n", Colours::black);
in both Source - UIComponents - CtrlrLua - MethodEditor - CtrlrLuaMethodCodeEditor.cpp and CtrlrLuaMethodFind.cpp

I do agree with you about Replace. I prefer a controlled replace than a blind one.

Thx for the git explanations.
I'm using Git desktop so don't use any command but will go through your points.
But with Damien we agreed to work thru issues where we paste our proposed code so, I continue on that.
He is then handling each issue one by one and I think it gives a good control.

[dnaldoog]

So far in testing the new search functionality is working well. https://github.com/dnaldoog/CtrlrX/tree/addsearchoption

I had massive confusion with Git and Git Desktop, but since working almost exclusively on the command line in PowerShell I am starting to get reasonably familiar with Git. After pushing to origin you can even command click on the output url or the push, which takes you to the Pull Request form on GitHub.

The great thing with PowerShell is that it remembers your history, just like Linux Bash, so you can just use the up arrow key to repeat /retrieve a previous command.