|
|
|
This thread is locked; no one can reply to it.
|
| [Code::Blocks] Is it possible to transfer compiler config |
|
larienna
Member #3,185
January 2003
 |
Now that I might have compilers on different platform and computers, I was wondering if there was a way to save, transfer and load into another compiler the interface configuration especially the color coding of the program code. Because it's a real pain to set every thing by hand when you have a custom color scheme. Enjoy! and have fun |
|
bamccaig
Member #7,536
July 2006
 |
You are mistaken. A compiler knows nothing of "interface configuration" or color coding (AKA syntax highlighting) of code. What you are used to is called an IDE or integrated development environment. For example, Code::Blocks, Eclipse, NetBeans, and Visual Studio. They generally each have their own completely unique configuration. I agree that it would be ideal if they all understood some standard common configuration that could be shared between them, but I don't think it is currently possible. If you just want to copy your Code::Blocks configuration from one machine to another than that should be possible, but I don't use Code::Blocks so I can't give you any specific guides right now. Code::Blocks is open source so you can expect to find a plain-text file or files containing the configuration. This is usually found in your home directory (i.e., ~ AKA $HOME in Unices) or %USERPROFILE% in Windows. In Windows it might also be found in your "Application Data" AKA "AppData" AKA "%APPDATA%" directory (the environment variable specifically points to the "Roaming" subdirectory in Vista and Seven, so you may need to move up to a parent and check the Local* variants). I store most plain-text configuration files of my own in a public GitHub repository so it is easy to share configuration among many machines. https://github.com/bamccaig/rc/ It does currently contain VS2010 configuration, albeit I generally work from the command line and predominantly only use Visual Studio at j0rb (when I know of no other way). For the record, there are 3 main processes used in C or C++ development: a preprocessor that processes preprocessor directives, a compiler that converts code into machine code, and a linker that combines that machine code into a single output (a program or library). The IDE is icing on the n00b cake, generally vendor-specific and generally more harmful than good. It is a GUI interface that sits on top of all of these processes and generally abstracts them into an Easy Button(tm). See also: http://wiki.allegro.cc/index.php?title=Header_file -- acc.js | al4anim - Allegro 4 Animation library | Allegro 5 VS/NuGet Guide | Allegro.cc Mockup | Allegro.cc <code> Tag | Allegro 4 Timer Example (w/ Semaphores) | Allegro 5 "Winpkg" (MSVC readme) | Bambot | Blog | C++ STL Container Flowchart | Castopulence Software | Check Return Values | Derail? | Is This A Discussion? Flow Chart | Filesystem Hierarchy Standard | Clean Code Talks - Global State and Singletons | How To Use Header Files | GNU/Linux (Debian, Fedora, Gentoo) | rot (rot13, rot47, rotN) | Streaming |
|
larienna
Member #3,185
January 2003
|
bamccaig said: You are mistaken. A compiler knows nothing of "interface configuration" or color coding (AKA syntax highlighting) of code. What you are used to is called an IDE or integrated development environment. True, I am sorry for the confusion. Maybe there could be more details in code::blocks's doc. One thing for sure, the config is not saved inside a project. Enjoy! and have fun |
|
Luiji99
Member #12,254
September 2010
|
Look in your AppData (Windows) or .codeblocks (GNU/Linux) and search for a file that looks like it has something to do with syntax highlighting. Programming should be fun. That's why I hate Java. |
|
Audric
Member #907
January 2001
|
Untested, but it appears to be in FAQ: |
|
|
You may find inspiration from it (or not).
