Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add example projects for different configurations #600

Open
niosus opened this issue Apr 29, 2019 · 11 comments
Open

Add example projects for different configurations #600

niosus opened this issue Apr 29, 2019 · 11 comments

Comments

@niosus
Copy link
Owner

niosus commented Apr 29, 2019

As of now, when setting up the plugin without CMake one needs to specify the needed flags. It might help the new users if there were simple examples to follow.

@stale
Copy link

stale bot commented Jul 14, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Just comment here to prevent this from happening.

@stale stale bot added the wontfix label Jul 14, 2019
@niosus
Copy link
Owner Author

niosus commented Jul 17, 2019

I still want to add those examples. Just hard to find the time :(

@stale stale bot removed the wontfix label Jul 17, 2019
@stale
Copy link

stale bot commented Sep 15, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Just comment here to prevent this from happening.

@stale stale bot added the wontfix label Sep 15, 2019
@niosus
Copy link
Owner Author

niosus commented Sep 17, 2019

Bump

@stale stale bot removed the wontfix label Sep 17, 2019
@stale
Copy link

stale bot commented Nov 16, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Just comment here to prevent this from happening.

@stale stale bot added the wontfix label Nov 16, 2019
@stale
Copy link

stale bot commented Nov 23, 2019

The issue has been automatically closed due to lack of activity. Feel free to reopen the issue if it is still relevant.

@stale stale bot closed this as completed Nov 23, 2019
@niosus niosus reopened this Nov 23, 2019
@stale stale bot removed the wontfix label Nov 23, 2019
@tomeksowi
Copy link

tomeksowi commented Dec 4, 2019

I agree, having simple from scratch examples would help a lot.

I just spent ~10 minutes trying to set up without CMake following the documentation, still stuck with the default ST3 auto-completion. It's not at all obvious where to even begin troubleshooting...

@stale
Copy link

stale bot commented Dec 4, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Just comment here to prevent this from happening.

@stale stale bot added the wontfix label Dec 4, 2020
@niosus
Copy link
Owner Author

niosus commented Jan 10, 2021

I still wonder when will I find the willpower to do this. 🤷

@stale stale bot removed the wontfix label Jan 10, 2021
@Feacur
Copy link

Feacur commented Apr 10, 2021

Hi! First of all, thank you for the plugin, @niosus and everyone involved, it works like a charm =)

Second, I've got my setup up and running, @tomeksowi, and anyone TWIMC: https://github.com/Feacur/game_prototype/tree/master/__sublime_project

  • game_prototype.sublime-project -> contains project-specific bits (include paths, global defines), see entries with the ecc_ prefix
    • N.B.: build_systems entries with file_regex could as well improve the QoL
  • __user_settings_reference -> some reference settings that go into the %appdata%/Sublime Text 3/Packages/User folder on Windows...
    • ... __Default (Windows).sublime-keymap -> remapping of some commands (with the ecc_ prefix, specifically)
    • ... EasyClangComplete.sublime-settings -> contains defaults for standard versions, a compiler path
    • ... Package Control.sublime-settings -> PackageDev and BuildX should be of use: first gives you better insights on Sublime Text and its plugins settings (so much easier to manage plugins and settings with it!), second redirects build output into a tab, which is handy; prolly, Terminus might be helpful occasionally

The very minimum should be like these two files:

// example of `*.sublime-project`
{
	"folders": [
		{
			"path": "."
		},
	],
	"settings": {
		"ecc_common_flags": [
			"-some-sompiler-flags",
			"-Isome/include/directories",
			"-DSOME_DEFINES",
		],
	},
	"build_systems": [
		{
			"name": "Build Clang",
			// between "^start" and "end$" tokens:
			// path:line:column: message
			// ^(.+):(\d+):(\d+): (.+)$
			"file_regex": "^(.+):(\\d+):(\\d+): (.+)$",
			"cmd": "path/to/your/compilation/routine"
		},
		{
			"name": "Build MSVC",
			// between "^start" and "end$" tokens:
			// path(line[,][column]): message
			// ^(.+)\((\d+),?(\d+)?\): (.+)$
			"file_regex": "^(.+)\\((\\d+),?(\\d+)?\\): (.+)$",
			"cmd": "path/to/your/compilation/routine"
		},
}
// example of `%appdata%/Sublime Text 3/Packages/User`
{
	"clang_binary" : "path/to/clang_executable",
}

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Just comment here to prevent this from happening.

@stale stale bot added the wontfix label Apr 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants