CImg library in c++:Actualy its really very simple, CImg allows you to only use CImg.h header and get the job done. But only just adding that header in your includes and compiling normally sometimes dont work(did not work for me). So if you are planning to use CImg and just want to get started, then do the following:
Add header: download the CImg.h header from the github repo. Add that in your includes,and link the header with your script using #include "includes/CImg.h.
Some_Folder/
|_>CImg.h
|_>demo.cpp
|_>demo.exe
#include<bits/stdc++.h>
#include "CImg.h"
using namespace std;
int main(){
/*
Add your functions here
*/
cout<<"hello CImg";
return 0;
}
g++ -o hello_world.exe HelloWorld.cpp -O2 -lgdi32 -std=gnu++0xor
g++ -o hello_world.exe HelloWorld.cpp -O2 -lgdi32 -std=gnu++11Source-> https://stackoverflow.com/a/22082194/12568833
Then, you can look at the documentation ‘html/reference/’ to learn more about CImg functions and classes. Finally, you can participate to the ‘Forum’ section of the CImg web page and ask for help if needed.
NB: If you are using GCC 4.7 or higher then `-std=gnu++0x` will work fine else not.
Check out the repo https://github.com/dtschump/CImg and 🌟 it
## 2. `C++` Auto-complete for Sublime text:
I am using [EasyClangComplete](https://github.com/niosus/EasyClangComplete). 💥 Robust C/C++ code completion for Sublime Text 3.
Plugin for Sublime Text 3 for easy to use, out of the box autocompletions for
C, C++, Objective-C, and Objective-C++.
## 3. Using `print()` instade of `cout<<`:
Sometimes people comes from python, face defficulty to adjust with `cout<<`, as they are used to of using `print()`, In c++ a good way to solve this problem is using c++ macros. Here is a snippit that I use, you can also define `endl` as `endline` (commented code) or `el`(as you like to call).
```cpp
#include <iostream>
using namespace std;
#define print(x) cout << x
// #define endline endl
int main()
{
print("Hello World!")<<endl;
print("hi");
// print(endline);
int n;
cin>>n;
int k;
return 0;
}
Image preprocessing from scratch using only c++:In future I wish to work on this, But after doing a bit searching in youtube I have found some great resources to learn it,
C;/mingw/bin/../lib/gcc/mingw32/6.3.0/../../../../mingw32/bin/ld.exe:D:\Documents\100DaysofDSA\Day_11_to_20\Day_17\inputf.in: file format not recognized; treating as linker script c:/mingw/bin/../lib/gcc/mingw32/6.3.0/../../../../mingw32/bin/ld.exe:D:\Documents\100DaysofDSA\Day_11_to_20\Day_17\inputf.in:1: syntax error collect2.exe: error: ld returned 1 exit status
Yeah man, this is it, this it itttt mah man…this is the error always keep bugging me, I know you are also frusted by watching that again and again. So here is what I found out while solving the problem,
c++ single file then try to switch to c++14 or c++17 build system.
Here is the c++14 build system:
{
"cmd": ["g++.exe","-std=c++14", "${file}", "-o", "${file_base_name}.exe", "&&" , "${file_base_name}.exe<inputf.in>outputf.in"],
"selector":"source.cpp",
"shell":true,
"working_dir":"$file_path"
}
Here is the c++17 build tools:
{
"cmd": ["g++.exe",
"-std=c++17", "${file}",
"-o",
"${file_base_name}.exe",
"&&" ,
"${file_base_name}.exe<inputf.in>outputf.in"],
"shell":true,
"working_dir":"$file_path",
"selector":"source.cpp"
}
Just go to tools->build systems->new build system, then paste any on the build system code and save that according to the c++ version name.
inputf.in and outputf.in file again. cut the tab from the sublime and again load the tab. And giving the input to the inputf.in move your curser to the respective cpp file, and then press ctrl+B to build.when you have certain condition, like untill this value becomes greater than some other value, or similar condition like that, then you use while loop and when you have to travers a path linearly with any kind of incriment then you use for loop.
while(i>j) means untill i is greater than j the loop will run.
I needed to change the color of the comments in my color scheme, I’m using cobult, so it was giving me darkish blue, but i wanted it to be greenish, so I changed it.
Package Resource Viewer from control install package. then shift+ctrl+p then type prv, Package Resource Viewer-Open source will show up, go to the color scheme - default and check out any color schemes, it will open a json, from there you can see the rules.// Documentation at https://www.sublimetext.com/docs/color_schemes.html
{
"name": "colult",
"author": "Sublime HQ Pty Ltd",
"variables":
{
// These colors are part of the hashed range
// and should only be used in non-source
"purple": "hsla(260, 50%, 60%, 1)",
"blue": "hsla(200, 70%, 45%, 1)",
"teal": "hsla(170, 70%, 45%, 1)",
"green": "hsla(130, 70%, 45%, 1)",
// End of hashed range colors
"red": "hsla(0, 70%, 65%, 1)",
"orange": "hsla(25, 90%, 60%, 1)",
"dark_orange": "hsla(10, 90%, 60%, 1)",
"yellow": "hsla(50, 100%, 60%, 1)",
"brown": "hsla(30, 30%, 45%, 1)",
"dark_brown": "hsla(30, 30%, 30%, 1)",
"magenta": "hsla(335, 100%, 65%, 1)",
"light_gray": "#f6f6f6",
"dark_gray": "#333",
"black": "black",
"pink": "#e371f5",
"lemon":"hsla(89, 100%, 58%, 0.92)"
},
"globals":
{
"caret": "color(var(lemon))",
},
"rules":
[
{
"scope": "comment",
"foreground": "#12fc73",
"font_style": "italic"
},
]
}
// Documentation at https://www.sublimetext.com/docs/color_schemes.html
{
"name": "colult",
"author": "Sublime HQ Pty Ltd",
"variables":
{
// These colors are part of the hashed range
// and should only be used in non-source
"purple": "hsla(260, 50%, 60%, 1)",
"blue": "hsla(200, 70%, 45%, 1)",
"teal": "hsla(170, 70%, 45%, 1)",
"green": "hsla(130, 70%, 45%, 1)",
// End of hashed range colors
"red": "hsla(0, 70%, 65%, 1)",
"orange": "hsla(25, 90%, 60%, 1)",
"dark_orange": "hsla(10, 90%, 60%, 1)",
"yellow": "hsla(50, 100%, 60%, 1)",
"brown": "hsla(30, 30%, 45%, 1)",
"dark_brown": "hsla(30, 30%, 30%, 1)",
"magenta": "hsla(335, 100%, 65%, 1)",
"light_gray": "#f6f6f6",
"dark_gray": "#333",
"black": "black",
"pink": "#e371f5",
"lemon":"hsla(89, 100%, 58%, 0.92)"
},
"globals":
{
"caret": "color(var(lemon))",
},
"rules":
[
{
"scope": "comment",
"foreground": "#12fc73",
"font_style": "italic"
},
]
}
// Documentation at https://www.sublimetext.com/docs/color_schemes.html
{
"name": "soumya monokai",
"author": "Sublime HQ Pty Ltd",
"variables":
{
// These colors are part of the hashed range
// and should only be used in non-source
"purple": "hsla(260, 50%, 60%, 1)",
"blue":"#05f7ff",
"blue1": "hsla(200, 70%, 45%, 1)",
"teal": "hsla(170, 70%, 45%, 1)",
"green": "hsla(130, 70%, 45%, 1)",
// End of hashed range colors
"red": "hsla(0, 70%, 65%, 1)",
"red2": "hsl(338, 95%, 56%)",
"orange": "hsla(25, 90%, 60%, 1)",
"dark_orange": "hsla(10, 90%, 60%, 1)",
"yellow": "hsla(50, 100%, 60%, 1)",
"brown": "hsla(30, 30%, 45%, 1)",
"dark_brown": "hsla(30, 30%, 30%, 1)",
"magenta": "hsla(335, 100%, 65%, 1)",
"light_gray": "#f6f6f6",
"dark_gray": "#333",
"black": "black",
"pink": "#e371f5",
"lemon":"hsla(89, 100%, 58%, 0.92)",
"black3":"#212121",
// "black4": "#282c3e",
// "lemon2":"#aaff00",
},
"globals":
{
"caret": "color(var(lemon))",
"background": "var(black3)",
// "selection": "var(blue)",
},
"rules":
[
{
"scope": "comment",
"foreground": "#4da81b",
"font_style": "italic"
},
// {
// "name": "Language variable",
// "scope": "variable.language",
// "foreground": "var(lemon2)",
// "font_style": "italic"
// },
{
"name": "Function call",
"scope": "variable.function, variable.annotation",
"foreground": "var(red)"
},
{
"name": "Library function",
"scope": "support.function, support.macro",
"foreground": "var(blue)"
},
{
"name": "Library constant",
"scope": "support.constant",
"foreground": "var(blue)"
},
{
"name": "Library class/type",
"scope": "support.type, support.class",
"foreground": "var(red2)",
"font_style": "italic"
},
]
}
// Documentation at https://www.sublimetext.com/docs/color_schemes.html
{
"variables":
{
},
"globals":
{
},
"rules":
[
]
}
writing functions is calle procedural programming and wrting classes called object oriented programming.