search

xpqz / DKaf

Dyalog Kafka
Apache License 2.0
0 stars 0 forks source link

Not an Issue !! #1

Open SalmanVolvoGit opened 2 weeks ago

SalmanVolvoGit commented 2 weeks ago

Hi Stefan, We came through this example and tried to implement it with the steps mentioned but we encounter Value Error in following line: ⎕NEW Consumer(0 '' ) VALUE ERROR: Undefined name: DyKa Ctor[6] consumer←⎕NEW DyKa.StringConsumer(bss groupid topic).

I assume it is not able to load the dll files which we run through using command ⎕USING. Is there any another approach we can follow or we can connect over to look at the issue ?

Will be eagerly waiting for your response on this.

xpqz commented 2 weeks ago

Hi @SalmanVolvoGit --

DyKa.dll is the C# "shim" layer. The build instructions are for macos. I assume you're using Windows? After you did a dotnet build and dotnet publish, in which directory did your DyKa.dll end up?

SalmanVolvoGit commented 2 weeks ago

Hi @xpqz , Thank you for your response. Yes, we are using Windows.

DyKa.dll did end up in mybuild folder as you have instructed in the steps mentioned. Capture1

And I used another approach in which I have kept the mybuild folder outside the DKaf directory(which I think is correct ) and is close enough to the solution I believe. DKaf directory of this is as shown below. image

For the later one, as per the Instructions from Vince(Dyalog Support associate), we set DYALOG_NETCORE as 1 and we are getting this error now. ]LINK.Create # C:\DKaf-main Link Warning: ⎕SE.Link.Create: .NET or .NetCore not available - watch defaults to 'ns' Linked: # → C:\DKaf-main ⎕USING←'Confluent.Kafka,C:/mybuild/Confluent.Kafka.dll' ⎕USING,←⊂',C:/mybuild/DyKa.dll'

  ]assemblies

He did mention to use 32-bit build of the dlls for 32-bit Dyalog but in the runtimes directory I don't see any folder with win-x32 as shown below:

image

Not sure where exactly are we going wrong in our approach.

xpqz commented 2 weeks ago

@SalmanVolvoGit you're nearly there, I think -- the 32-bit build is called win-x86, somewhat confusingly. Try that. Feel free to contact me directly (stefan@{that APL company}.com)