Author Topic: Best way to teach C::B to handle some files in specific way when building?  (Read 5959 times)

Offline 0x0000053A

  • Single posting newcomer
  • *
  • Posts: 8
I have some GLSL shaders in my current project.
I want to objcopy them and link with my code so i can use their contents in my program without placing it directly in cpp files as string constant.
Unfortunately, C::B does not handle these files at all, nor does it react to changes in them by rebuilding the project.
Is there a way to tell C::B that it needs to process these files without manually rewriting the whole build process in custom makefile?

I thing that custom makefile is a really convenient option to use in the near future, but right now I'm just interested if my goal is reachable with standard ide tools.

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 3353
Re: Best way to teach C::B to handle some files in specific way when building?
« Reply #1 on: February 01, 2018, 08:37:24 pm »
Many ways to rome...

One way, a bit risky, but normally the way to go:
Settings->Compiler->Other settings->Advanced options

From the dropdown menu Command: Compile single file to object file
Source ext: klick the "+" and add the file extension you have for your GLSL files

You can look at the other extensions how this works.

If you give us the command line we maybe can help you...

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]