Hi!

This is FASM Add-In. It adds support for the FASM Assembler and other compilers via advanced support for compilation with batch files. Please let me know of any suggestions/bugs so that we can all benefit

Features:
- Support for compilation with fasm compiler
- Support for compilation using bat-files
- Support for autocompiling sources (mixed bat/asm)
- Support for usage of emulators to run/debug executables
- Support for alternate 16-bit debugger for DOS projects
- Automatical export for resource definitions in assembler format
- Automatical include file with build version to support release/debug builds
- Automatical fasminc environment variable made from path to compiler
- Alternate project properties box to setup additional properties

Supports dinamic Multylanguage User Interface of IDE

Add-In, templates to use with it and examples can be downloaded here

Here can be downloaded latest version (1.4)

To convert existing sources INP2 AddIn recommended

If you wish to write an Add-In for WinAsm Studio using FASM,
please check for the latest WAAddInFASM.inc

This post has been edited by shoorick on Oct 9 2005, 11:56 PM

Attached Image

Let's cooperate step by step to make it work then!

On WinXP, WinAsm Studio crashes when I try to load the Add-In from Add-Ins Manager.

Antonis

too complex code :D

This post has been edited by shoorick on Feb 23 2005, 07:19 AM

Attached Image

Ok, step 1 successful!

Waiting for the next one

Antonis

step2: does the same, but includes new converted WAAddInFasm.inc.
compiled without errors, so, it is also a little success ;)

by the way: how can i redirect console output into out window (ready code, if possible, to save my time :) ) thanks!

Thanks for the 2nd step

http://www.winasm.org/forum/index.php?show...view=getnewpost is how I redirect console output to the Output window

Antonis

hi! i need clear information about enabling/disabling options in "Make" submenu and toolbar: i understand that i can override them after recieving WAM_DIFFERENTCURRENTPROJECT message... so, what about starting winasm studio with no project, with opening just asm file, when project is just closed. and, at last, how i can force studio to make en/dis by its rules when addin, for example, switch off or unloaded...

thnx!

I hope you don't need any of the above after our Private conversation. Do you?

Antonis

yes, agree, also you can remove this 3 replies :)

Hi! here is a next step, raw, but already usable a little ;)

1.place wafasm.dll into AddIns dir
2.in AddIns manager locate "FASM compilation"
3.press "Configure" and enter full pathname to the win32console version of FASM compiler (DOS version also can be choosed, but w32 better)
4.check "Loaded" and press "OK"

now you have able to call FASM compiler to your projects instead of MASM. you can switch compilers manually by checking/unchecking FASM menu item in AddIns submenu. when FASM loaded it will checked always (a while). only assemble/link options avaible a while, other will just show a message to you (a while ;) ) so, too many "a while", but you can start to play! also, any other compiler/batch file can be choosed, not exactly FASM, but command line does not used yet. also, it was appeared that %fasminc% was unavaible to compiler, so, i've replaced all "%fasminc%" to "\fasm\include" in all pathes in all files inside include dir (also, it is maybe "a while" :D )

well, enjoy!

next step here. so, what's new:
1.assemble, link and go all do same - compiling (go all - a while)
2.run and debug works now - they use output name from release out field
3.remeber last state, so, can be turned on to run at start up - if it was switched off before it will not annoy you ;)

so, not finished, but already usable - enjoy!

This post has been edited by akyprian on Feb 18 2005, 05:23 AM

Hi,

So far so good!

1.As far as your Add-In is concerned, are Assemble and Link the same thing?

2.Go all and Execute do not launch the executable produced.

Antonis

as FASM is concerned ;)

a while ;)

new update of wafasm above!
about %fasminc% - i just had wrong value in my environment (with extra space at the end), that's only why i could not use it - already corrected...

MUCH Better.

1.If nothing is specified in /OUT then compiled project is not launched

2.If Go all is pressed, you have to check in the winasm.ini whether LaunchExeOnGoAll=1 in the [MISCELLANEOUS] section. If so, and provided the project is executable, launch the compiled project

Thanks,

Antonis