YafaRay Plug-in

[micheus]

All Wings3d?? Non, merci..
I have 15 'compilers environment' in my PC ( more or less)..

povmaniac, I think you don't need.
As you already have cloned the wings repository from git, you would just have to enter in the wings/plugins_src/import_export and run make.

I did a test here (on my dev. environment) by leaving only the wings source folder and removed any .beam file previously generated and I was able to compile all the export/import plugins.
_____________

I noticed that you will need to add the yafaray to the makefile file:

Code:

:
MODULES= \
    wpc_3ds \
        :
    wpc_x \
    wpc_yafray \
    wpc_yafaray

TARGET_FILES= $(MODULES:%=$(EBIN)/%.beam)
:

By supposing that you didn't cloned esdl, you would need to remove the $ESDL_PATH references in the makefile:

Code:

:
WINGS_E3D=../../e3d
# *** removing ESDL reference
# ESDL=$(ESDL_PATH)

ifeq ($(TYPE),debug)
:
# ----------------------------------------------------
# FLAGS
# ----------------------------------------------------
#ERL_COMPILE_FLAGS +=  -pa $(WINGS_EBIN) -pa $(WINGS_INTL) -I $(WINGS_INTL) -I $(WINGS_SRC) \
#  -I $(WINGS_E3D) -I $(ESDL_PATH)/include -W $(TYPE_FLAGS) -pa $(ESDL_PATH)/ebin \
#  +debug_info
# *** replacing with these lines ***
ERL_COMPILE_FLAGS +=  -pa $(WINGS_EBIN) -pa $(WINGS_INTL) -I $(WINGS_INTL) -I $(WINGS_SRC) \
  -I $(WINGS_E3D) -W $(TYPE_FLAGS)  \
  +debug_info

You will find the output beam at wings/plugins/import_export.

You may need to check these environment vars:
PATH -> should include the erlang bin folder (i.g. /c/.../erl5.10.1/bin) and the C compiler location (i.g. /c/MinGW/bin)
WINGS_SRC_PATH -> should point to the wings source root (i.e. /c/sources/wings)

Please check this. I'm sure that would be good if you could get the compilation feedback by yourself.

Thanks for help our community.