Author Topic: sc.ini Digitalmars toolchain  (Read 1394 times)

Offline Suryavarman

  • Multiple posting newcomer
  • *
  • Posts: 31
    • Suryavarman
sc.ini Digitalmars toolchain
« on: October 28, 2016, 10:55:32 am »
Hi!

First I'm sorry for my poor english ;).

I work on my project https://sourceforge.net/projects/gdeps/ and i have a question for the CB team:

In Digitalmars case, why we cannot override the sc.ini toolchain in CB? Is it possible?
I see this problem:

Example:
If I have a CB project using stl implementation and another one don't use the stl implementation.

To do that I have to create a Digitalmars installation folder for each custom toolchain?



Offline stahta01

  • Lives here!
  • ****
  • Posts: 6613
    • My Best Post
Re: sc.ini Digitalmars toolchain
« Reply #1 on: October 28, 2016, 04:56:13 pm »
Delete or editing the "sc.ini" file is the only way I found using Google; I am NOT an Digitalmars user.

Tim S.
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline Suryavarman

  • Multiple posting newcomer
  • *
  • Posts: 31
    • Suryavarman
Re: sc.ini Digitalmars toolchain
« Reply #2 on: October 28, 2016, 05:55:05 pm »
Ok...
I have made an exception. I have use google and not Qwant ... and what? What have you find? 
Can you post your google search ?

Thanks a lot.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 6613
    • My Best Post
Re: sc.ini Digitalmars toolchain
« Reply #3 on: October 28, 2016, 09:35:48 pm »
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline Suryavarman

  • Multiple posting newcomer
  • *
  • Posts: 31
    • Suryavarman
Re: sc.ini Digitalmars toolchain
« Reply #4 on: October 29, 2016, 11:55:23 am »
Ok thanks. I appreciate.

Quote
Sure I get the point, and most of the time I appreciate it. However, at the
moment I'm wanting to do some testing of DMC++ with and without STLPort, and
I was wanting a quick and easy solution. The alternative, of course, is
specify ...\dm\stlport in the include list, but it'd be much easier with
a -e (a la MAKE).

If i understand well he add the stlport paths in the include list. I don't understand the meaning of «but it'd be much easier with
a -e (a la MAKE)». I think, in the same way, i have try that with CB. I have add the includes and the libraries directories in Project Build Otpions -> Searching Directories or Settings -> Compiler... -> Search Directories . But it doesn't work. And it's the same problem with the environments variables.

My solution it's to use a pre/post build script to edit the sc.ini.