Diderot

I realise that Diderot was written to compliment the DDE. Would it be possible to also support the GCC enviroment?

In the Makefiles there is a GCCRules file and it works.
Your makefile must refer to GCC:
ex:
CC := g++
CFLAGS := -mthrowback -mlibscl -O3 -std=c99 -DCCDOC_CID=\“RISCOSport_bin_v0.1.3_2002/05_noopt_gcc4.7.4_RiscOs4\”
ASASM := asasm
LINKFLAGS := -mlibscl

OBJS = database.o exceptions.o help.o log.o \

all: ccdoc

ccdoc: $(OBJS)
$(CC) $(LINKFLAGS) $(OBJS) -o $@

.c.o:
$(CC) $(CFLAGS) -o $@ -c $<

.cc.o:
$(CC) $(CFLAGS) -o $@ -c $<

Thank you, I’ll give what you’ve suggested a try. I thought that perhaps Diderot might recognise the environment loaded, either DDE or GCC, so that if a Makefile existed in a development directory, it would know what to do with it, activating the Make button.

Diderot creates environment variables for each projects. We can therefore have several projects open at the same time without monopolizing the desktop.
"*show projdev*

Diderot makes the filer commands execute when pressing the buttons, so if your makefile works (DDE or GCC) you will have the same result.

Diderot’s goal was to have project and commands information in the same space, otherwise I had to have all the application directories open and desktop shorcuts. Rick Griffin’s treeview module is perfect for this.

Diderot uses the standard development directories’ structure see DDE examples
The Make button is grayed if the Make file does not exist, ditto for the others.
File names can be changed in the !Diderot Messages file.

I hope my explanations are understandable.
Thanks for testing.